- This topic has 5 replies, 3 voices, and was last updated 17 years, 10 months ago by
.
-
Posts
-
I work on a project with a great deal of Sybase stored procedures. One feature which would be nice is to have the “Open Declaration” ability with stored procedures. When tracing through a stored proc, I have to copy the procedure name, search source SQL files for the procedure name and then open the file to continue tracing. With the “Open Declaration” functionality, this would greatly reduce the amount of time I spend debugging an issue.
The functionality already exists in the JDT for Java Source files. It’s activated by pressing ‘F3’ (by default), or right clicking and selecting “Open Declaration”.
I haven’t seen this feature requested anywhere. Forgive me, if this has been requested in the past.
I suppose that you want this feature in SQL Editor and it is not possible for now, but you can find and open stored procedure declaration from Db browser with right click nad Open command (for MyEclipse >= 5.1.0)
Regards,
you can find and open stored procedure declaration from Db browser with right click nad Open command
If you mean the declaration defined in the database, that’s not what I’m implying. I would like to see it open up the source SQL on the filesystem. My apologies if I misunderstood you.
I don’t underastand you.How MyEclipse (or what ever) can open procedure on filesystem ? – data about procedures are in database.
JDT know from package and name of class where binary (and source if it is attached) class is, but there isn’t some data about procedure’s source files.
You can organize your source files (scripts) how you want and there isn’t rule for this like rules in Java.Sorry if I don’t understand something
Regards,
The logic could index SQL files. This index could be used to locate the files in the project which define the stored procedure. The open declaration functionality would query the interal index similar to how Eclipse/JDT opens files.
I haven’t seen how JDT implements this functionality, but I would presume creating some sort of index is involved. When using the “Open Type” functionality, Eclipse occassionally rebuilds the index (if you’ve recently opened your project). Just because Java has a set standard for where to place your source files, doesn’t mean the files would be easy to find. You can have the same package defined in multiple source folders in your project. Also there is the issue of inner classes which do not have a file all to themselves.
