Some time ago I tried 6.0 and 6.1 betas, but it seems that the final 6.1 release got even worse.
As I understand a new formatter has been implemented, but it fails to work for me.
The formatter options have Header/Tagline, which by some reason places the comment line at the end of code, instead of… you know, being a header and place it in front.
Following 1, the explain plan tool fails to work if there is a comment at the end of code -
3:38:27 PM Error in SQL: ORA-01742: comment not terminated properly
/* Formatted on 1/7/2009 3:25:10 PM (QP5 v5.120.811.25008) */
The same comment placed at the end fails in SQL Nav 5.5, but no issue if it is in front in both 5.5 and 6.1
- The formatter adds some special symbols, I think for tabs, that are visible as square symbols (and no tabbbing) on the editor window, but the same formatted code look normal in explain plan window, in addition to that there’s totally different key word hi-lighting on code editor and explain plan windows.
see the attached image (explain plan on top, code editor on the bottom)
- The new code editor window fusioned with DB explorer fails to control window focus.
Sometimes it treats key presses done in code editor window as key presses on the DB tree, i.e. instead of deleting a character on ‘Del’ key press SQL Nav prompts to drop a DB object instead. Very funny.
That’s what I found in just 5 minutes. I guess I’ll go back to 5,5, even that it crashes all the time for me.