|
From: Robert M. <rob...@gm...> - 2007-02-24 01:49:58
|
On 2/23/07, David Schmitt <dav...@ho...> wrote: > I'll keep an eye out for the QueryTokenizer plugin. As far as I know the Just to be clear - QueryTokenizer *was* a utility class that was used to break up the selected region of the editor into individual statements to send to the database. Now it is more of a framework to allow plugins to implement their own query tokenizing behavior. (One example is statement separator which is different depending on what database you are using - "GO" for Sybase/MS-SQLServer, ";" for others). This is available now in CVS; the first release to include it will be 2.5 slated for late March. I was commenting that the new DB2 plugin might be able to take advantage of it by providing support for "CALL ...". The Oracle plugin uses this framework to parse "create procedure/function" statements by allowing any embedded ";" and terminating the statement on "/". The main issue with executing stored procs this way is that we would need to use CallableStatement instead of merely executing everything with Statement. I'll have to look at SQLExecuterTask to see how do-able this would be. It would be nice for all of the plugins to support stored procedure execution, but that's not likely to make it into version 2.5. Rob |
