[ http://issues.apache.org/jira/browse/DERBY-2060?page=all ]
Kim Haase updated DERBY-2060:
-----------------------------
Attachment: DERBY-2060-2.diff
DERBY-2060-2.zip
Added DERBY-2060-2.diff and DERBY-2060-2.zip. These reflect corrected
information about transaction isolation, I hope. Four files have been modified
now:
Two adjacent sections in the Developer's Guide:
devguide/cdevconcepts15366.html
devguide/cdevconcepts22300.html
Two sections in the Reference Manual:
ref/rrefsqlj41180.html (SET ISOLATION statement)
ref/rrefjavcsti.html (Connection.setTransactionIsolation method)
cdevconcepts15366.html and cdevconcepts22300.dita also have a few spacing
corrections to improve readability.
> SET CURRENT ISOLATION in ref.man refers
> java.sql.Connection.setTransactionLevel instead of
> java.sql.Connection.setTransactionIsolation
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2060
> URL: http://issues.apache.org/jira/browse/DERBY-2060
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Reporter: Bernt M. Johnsen
> Assigned To: Kim Haase
> Attachments: DERBY-2060-2.diff, DERBY-2060-2.zip, DERBY-2060.diff,
> DERBY-2060.zip
>
>
> On SET CURRENT ISOLATION statement in the Derby refernce manual:
> "Issuing this command commits the current transaction, which is consistent
> with the java.sql.Connection.setTransactionLevel method."
> The correct method name is java.sql.Connection.setTransactionIsolation
> (java.sql.Connection.setTransactionLevel does not exist)
> BTW: setTransactionIsolation will commit the current transaction if called in
> the client driver but not in the embedded driver. See DERBY-638
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
