db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (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 Wed, 02 Jan 2013 15:28:13 GMT

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

Rick Hillegas commented on DERBY-5690:

Hi Kim. Since the need for StatementReader has come up a couple times, it might make sense
to move it to org.apache.derby.tools, add it to the public api, and document it as you suggest.
There's a lot of overlap with StatementFinder, so we would probably want to refactor the two
classes to eliminate the overlap. Sounds like a pleasant afternoon's work. 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: SQLRunner.java, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message