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.
Thanks David, I know that. But I would like to use SVN to store all my sources. If I'll use sp editor, than my filesystem copy will be out of sync with database copy.
David, thanks again!I found what you did mean - it is possible to edit files using "pl*sql editor", which is not the same as "sql script editor".
The same thing for me ...
I have a lot of stored procedures fore testing who are very long. And also a lot of Query's who are very long. I save anything with *.sqlIf I open the QUERY.sql with SQL Editor I have the problem with the jump on first line on execute SQL Script. And executing in SP Editor doesn't works.On opening die StoredProcedure saved as *.sql as default opens the SQL Editor where It always jumps to first line, on OPEN IN SP Editor what is not the default settings it want jump to first line.For me is better to NEVER Jump to first line, but stay always at the actual line. If not, the alternatively is to have a property for it.Michael
I save anything which is not a package function or procedure as *.SQL
So anything I do, test query's or test store procedures I will save as *.SQL and will open in the SQL Editor.And anything in the SQL Editor on execution will jump to first line, but I will never jump to first line.Michael
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.
The idea "link to original file" IS GREAT!!!!!!!!!!!!I vote for 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 version: 4.2.2 Build M20130204-1200Tee version : 188.8.131.52310070822
certainly David,The point 1, tighter integration with version control should go to the idea pond... If I only knew where it is... If you can tell me, i'll move it there.Thanks,Yoann