If external .sql file in SQL Script editor contains a big sql statement (for example package implementation with a lot of procedures), then after "Execute SQL Statement" scroll vertical position is changed and first line of SQL statement is made visible. It is unwanted and confusing for user.
there are two editors for opening files. Files with .sql suffix are by default opened in the SQL Editor, files with other suffixes (.vw, .fnc, ...) are opened in the PL/SQL Editor. SQL. (Note: default editors can be changed in Eclipse settings.)
For packages, we use suffix .pks (spec) or .pkb (body). The particular suffix is not as important, but you make sure that the file is opened on the correct editor.
Michael, yes, I know, it is probably a common thing - anything regarding sql is saved as ".sql". I don't know if I understand your problem correctly, but I will test it. I think if there is some problematic behaviour, it can surely be fixed. Tomas
Tomas, thanks for your suggestion about default editors - I changed file extention and now correct editor opens by default.
Is it possible somehow to setup eclipse when I click on database object in schema browser to not open new sql object browser window, but navigate to file, which was used to generate this object.
If it is not possible, then it can be idea for toad: add a new lockable button in schema browser: "link to original file". If user checks this button - toad first may try to find definition of the object in workspace's files and navigate to it.
+1, this would be just perfect! The whole thing I see for this is the following: - Possibility to define the directory in wich are the objects (package Body, packeSpecs, ...) - when ctrl-click on an object, instead of opening object from DB, open the file containing the object if found in the defeined directory.
The file name should be the same has the object name, case insensitive, free extention.
The reason I'm asking this is because we are using Clearcase with a directory structure alowing us to store both our ORACLE code and the other code, and the structure for the database code was made with another tool that doesn't have the same way of storing things as TEE.
If it's not the rigth place to put this, feel free to move to the correct place ;-) Thanks a lot, Yoann
Eclipse SDK Version: 3.7.2(32bit) Build id: M20120208-0800