In PL/SQL Developer Version 14.0.6.1988 (64 bit) the search is sometimes just doing nothing. Here are the steps to reproduce:
1. Mark the text to search for in code
2. Ctrl + F
3. Edit the field "Text to find" (just modify, do not replace the given content)
4. Add text into "Replace with"
5. All Options unchecked, Search in: Comments unchecked, Scope: From Cursor, Direction: Forward, Wrap unchecked
6. Click on "Search next"
In at least 50% of these "search for individual replace" cases (rather more) the search simply does nothing, even though there are matches in the code. Everything stays responsive but the search does not jump in.
Expected behaviour would be that the next match is marked for further action.
Generally my experience is, that in less specific scenarios the Scope "From cursor" does not work, i.e. is just doing nothing as described above. And even more general the Search shows a significant number of inactivity after hitting "Search next" which should be looked at. Unfortunately this behavior is still random. So far I can't tell, which exact scenarios reproducibly do not work.
This might be mitigated by some more output what the search is currently doing, but in the end the search should be made more reliable to get the results, that match the actual search configuration. It seems like modifing the search options in the same "search process" (i.e. without closing the search window) makes it more likely that the search gets confused. Rarely a "Search all" helps getting back on track.
Is there a possibility, that the search struggles when searching in invalid packages? I came across all this during heavy refactoring in a rather large package. But this is just a guess and the issue described above doesn't occur exclusively in the "invalid package" scenario.
If there is a way to get kind of a "search log" for debugging this, let me know how to provide it.
1. Mark the text to search for in code
2. Ctrl + F
3. Edit the field "Text to find" (just modify, do not replace the given content)
4. Add text into "Replace with"
5. All Options unchecked, Search in: Comments unchecked, Scope: From Cursor, Direction: Forward, Wrap unchecked
6. Click on "Search next"
In at least 50% of these "search for individual replace" cases (rather more) the search simply does nothing, even though there are matches in the code. Everything stays responsive but the search does not jump in.
Expected behaviour would be that the next match is marked for further action.
Generally my experience is, that in less specific scenarios the Scope "From cursor" does not work, i.e. is just doing nothing as described above. And even more general the Search shows a significant number of inactivity after hitting "Search next" which should be looked at. Unfortunately this behavior is still random. So far I can't tell, which exact scenarios reproducibly do not work.
This might be mitigated by some more output what the search is currently doing, but in the end the search should be made more reliable to get the results, that match the actual search configuration. It seems like modifing the search options in the same "search process" (i.e. without closing the search window) makes it more likely that the search gets confused. Rarely a "Search all" helps getting back on track.
Is there a possibility, that the search struggles when searching in invalid packages? I came across all this during heavy refactoring in a rather large package. But this is just a guess and the issue described above doesn't occur exclusively in the "invalid package" scenario.
If there is a way to get kind of a "search log" for debugging this, let me know how to provide it.
