[
https://issues.apache.org/jira/browse/DERBY-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004365#comment-13004365
]
Bryan Pendleton commented on DERBY-4443:
----------------------------------------
I think that the system procedures are called through a clever sort of
reflection mechanism, which is why
you don't see a direct call mechanism in place. Here's a link to these
procedures, showing how to
invoke them:
http://db.apache.org/derby/docs/10.7/ref/crefsqlbuiltinsystemprocedures.html
Regarding an existing test suite, I think that this test suite should run these
procedures:
org.apache.derbyTesting.functionTests.tests.tools.ImportExportProcedureTest
The code for that test is in
java/testing/org/apache/derbyTesting/functionTests/tests/tools/ImportExportProcedureTest.java
> Wrap rollback in exception handlers in try-catch
> ------------------------------------------------
>
> Key: DERBY-4443
> URL: https://issues.apache.org/jira/browse/DERBY-4443
> Project: Derby
> Issue Type: Bug
> Components: Demos/Scripts, Documentation, Eclipse Plug-in, JDBC,
> Network Client, Network Server, Replication, Services, SQL, Test, Tools
> Affects Versions: 10.5.3.0
> Reporter: Aaron Digulla
> Labels: derby_triage10_8
> Attachments: DERBY-4443.patch
>
>
> Avoid this pattern everywhere:
> }catch(SQLException se){
> //issue a rollback on any errors
> conn.rollback();
> throw se;
> }
> because an error in rollback will shadow the original exception.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
