Bug #87060 [docs] make clear that COMMIT AND CHAIN maintains READ ONLY property
Submitted: 13 Jul 2017 10:55 Modified: 18 Jul 2017 19:40
Reporter: Federico Razzoli (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any
Tags: missing-docs

[13 Jul 2017 10:55] Federico Razzoli 
Description:
Here:
https://dev.mysql.com/doc/refman/5.7/en/commit.html

I read:

"The AND CHAIN clause causes a new transaction to begin as soon as the current one ends, and the new transaction has the same isolation level as the just-terminated transaction."

From this sentence, it is not clear that:

START TRANSCTION READ ONLY;
...do something...
COMMIT AND CHAIN;

starts a new READ ONLY transaction.

How to repeat:
.
[14 Jul 2017 6:27] MySQL Verification Team 
Hello Federico,

Thank you for the report and feedback!

Thanks,
Umesh
[18 Jul 2017 19:40] Daniel Price 
Posted by developer:
 
The referenced content was updated as follows:

"The AND CHAIN clause causes a new transaction to begin as soon as the
current one ends, and the new transaction has the same isolation level as
the just-terminated transaction. The new transaction also uses the same
access mode (READ WRITE or READ ONLY) as the just-terminated transaction."

Thank you for the bug report.