[
https://issues.apache.org/jira/browse/DERBY-5731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julius Stroffek updated DERBY-5731:
-----------------------------------
Attachment: derby-5731.diff
Attaching the patch.
It creates a new exception ijExitException which is thrown in a similar way
than ijFatalException. The further error about exiting ij is dumped in the main
function where ijExitException is caught.
There might be few more things:
* The attached patch does not exit if there is a failure in connection.
However, it exits when there is a statement to be executed on that failed
connection.
* There might be a need for test cases. However, I am not able to find any test
cases for ijFatalException either. I am therefore not sure whether the test
cases are needed.
* There is a need to update the documentation with information about
ij.exitOnFailure property.
Please give me some comments to the patch and also please advice what needs to
be done before accepting this patch.
> 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
