db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5690) Give users a way to run an ij script programmatically so they can filter errors.
Date Thu, 12 Apr 2012 15:37:17 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252496#comment-13252496

Rick Hillegas commented on DERBY-5690:

Hi Dag,

Yes, StatementFinder has different constructors. Getting rid of those constructors is a large
part of what you need to do in order to break the dependency on Derby internals and expose
this useful functionality to end-users. Thanks.
> Give users a way to run an ij script programmatically so they can filter errors.
> --------------------------------------------------------------------------------
>                 Key: DERBY-5690
>                 URL: https://issues.apache.org/jira/browse/DERBY-5690
>             Project: Derby
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions:
>            Reporter: Rick Hillegas
>         Attachments: StatementReader.java
> Sometimes users need a way to run an ij script programmatically and handle the errors.
It would be nice if they could use ij's StatementFinder to parse a semi-colon delimited file
of sql statements, throwing away comments. StatementFinder itself can't be used because it
is not part of the public api and it has some small dependencies on other Derby code. I will
attach a standalone class which applications can use.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message