I think, i have an issue with possible bug - if i select fully qualified view name in the sql window (maybe either a view name in own schema) - and click on the menu point - view "...my view..." -> view - then by some views it loads extremely long time the content of view into sql window. I started plsql developer in sessionmode single and traced the session - it showed, plsql developer tries to execute twice the view - 1st time - "select * from <my_view>", 2nd time - "select <underlying query from my view>" - both times without any predicates (like rownum <1 or similar). From my perspective - this should be absolutely not necessary to obtain the source code of the view, besides that - some views are not designed at all to be queried without any predicates. As result - plsql developer freezes for long time (in cases where such query is time consuming/ineffizient).
Second issue - i think this could be a regression after sql window got support for bind variables - in the previous versions it was possible in the sql window to execute something like
"explain plan for select * from dual where dummy=:b1". Now it results in prompt for bind (whereas in this case the bind value is mostly not necessary) - and if i disable bind interpretation - it results in ORA-01036. This is very inconvienient though workarounds exists - in command window and explain plan window it works as expected.
Tested in 16.07 and 16.08 (x86-64).
Regards
Maxim
Second issue - i think this could be a regression after sql window got support for bind variables - in the previous versions it was possible in the sql window to execute something like
"explain plan for select * from dual where dummy=:b1". Now it results in prompt for bind (whereas in this case the bind value is mostly not necessary) - and if i disable bind interpretation - it results in ORA-01036. This is very inconvienient though workarounds exists - in command window and explain plan window it works as expected.
Tested in 16.07 and 16.08 (x86-64).
Regards
Maxim
