[
https://issues.apache.org/jira/browse/DERBY-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-3579:
-----------------------------
Attachment: DERBY-3579-2.stat
DERBY-3579-2.zip
DERBY-3579-2.diff
Attaching DERBY-3579-2.diff, DERBY-3579-2.zip, and DERBY-3579-2.stat.
I hope I have corrected the statement that was misleading in cdevspecial847513.dita. I made a few other corrections to the last sentence, and to an index entry that had nothing to do with this topic. I also changed "by using the CallableStatement method" to "by using a CallableStatement", because "method" is ambiguous and seems to have meant "technique" here (CallableStatement is an interface, not a method).
I have gone ahead and changed "procedure" to "routine" wherever it seemed appropriate to do so, but I hope someone will review the changes carefully and let me know if any corrections are needed.
In addition to the changes previously described, I have also modified the following Developer's Guide topics:
cdevspecial847513.dita, "Invoking a procedure using the CALL command":
cdevspecial.dita, "Derby server-side programming": changed "procedure" to "routine"
cdevspecial42117.dita, "Programming database-side JDBC procedures": changed "procedure" to "routine" where needed and made some other fixes
cdevspecial29620.dita, "Database-side JDBC procedures and nested connections": changed "procedure" to "routine" where needed and made other fixes (removed duplicate index term, capitalization, inconsistent fonts, etc.)
cdevspecial16181.dita, "Database-side JDBC procedures using non-nested connections": changed "procedure" to "routine" where needed, fixed font inconsistency
cdevspecial41728.dita, "Database-side JDBC procedures and SQLExceptions": changed "procedure" to "routine" where needed, fixed font inconsistency
cdevconcepts29416.dita, "Using auto-commit": changed "procedure" to "routine" where needed
cdevconcepts32861.dita, "Programming applications to handle deadlocks": removed text from cross-reference to cdevspecial41728.dita
cdevconcepts36881.dita, "Connections": changed "JDBC procedure" to "JDBC routine" (one occurrence), fixed font inconsistency
cdevconcepts38375.dita, "The JDBC Connection and Transaction Model": changed "JDBC procedure" to "JDBC routine" (one occurrence), fixed font and capitalization inconsistencies
cdevdgpref11181.dita, "Purpose of this guide": changed "JDBC procedure" to "JDBC routine" (one occurrence)
Also in the Ref Manual:
crefjavgcasyn.dita, "Additional SQL syntax": changed "database-side JDBC procedure or method" to "database-side JDBC routine"
> 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
> Affects Versions: 10.3.2.1
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: DERBY-3579-2.diff, DERBY-3579-2.stat, DERBY-3579-2.zip, DERBY-3579.diff, DERBY-3579.zip, 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.