[
https://issues.apache.org/jira/browse/DERBY-5731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264587#comment-13264587
]
Julius Stroffek commented on DERBY-5731:
----------------------------------------
Hi Knut,
I think exitonerror command might be good. However, I would keep the system
property as well. I think that ij command could be used to execute scripts on
other JDBC databases (although I have not tested that) and thus the script does
not have to be prepared specially for derby. When invoking such a script you
could simply set JVM property without altering the script. This is also the
case when you would like to run scripts automatically generated from some type
of O-R mapping like Hibernate. My use case is execution of Hibernate generated
scripts and system property fits better to me.
For programatic API what you would think about adding an "optional" argument ro
ij.runScript that will turn on exit on error. This will avoid usage of derby
specific commands in scripts.
btw: I forgot to exit with the exit code in the patch. I fixed that myself, but
I need to change that anyway as it will not work for programatic invocation of
ij.runScript.
> It should be possible to start ij in a mode when it terminates in case of any
> error
> -----------------------------------------------------------------------------------
>
> Key: DERBY-5731
> URL: https://issues.apache.org/jira/browse/DERBY-5731
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Reporter: Julius Stroffek
> Assignee: Julius Stroffek
> Labels: ij
> Attachments: derby-5731.diff
>
>
> It should be possible to determine from the exit status of ij whether the
> commands that were executed failed or not. This should not be the default
> behavior as it will break the compatibility.
--
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
