[
https://issues.apache.org/jira/browse/DERBY-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-3579:
---------------------------------
Attachment: z.java
Attaching z.java, which contains a database procedure, commitProc(), which can
be used to demonstrate the behavior of commit()/rollback() in user-coded
routines.
> The Developer's Guide incorrectly describes the behavior of transactions
> inside procedures and functions
> --------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3579
> URL: https://issues.apache.org/jira/browse/DERBY-3579
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Reporter: Rick Hillegas
> Attachments: z.java
>
>
> The "Programming database-side JDBC procedures" section of the Developer's
> Guide misleads users about how transactions can be managed inside database
> procedures. For instance, the section titled "Invoking a procedure using the
> CALL command" says the following: "Procedures that use nested connections, on
> the other hand, are not permitted to commit or roll back and can therefore be
> rolled back after the calling statement." This is not true. User-coded
> procedures can issue both commit() and rollback() on the nested connection
> bound to the "jdbc:default:connection" URL and those methods have the desired
> behavior. The whole "Programming database-side JDBC procedures" section could
> use an overhaul since it appears to make other misleading statements about
> the behavior of transactions inside routines. Thanks to Dag for pointing out
> the following email thread:
> http://www.nabble.com/Transaction-Problems-of-a-Derby-Stored-Procedure-td15494178.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
