Bug #87310 | References to 5.7.20 in doc before release | ||
---|---|---|---|
Submitted: | 3 Aug 2017 21:51 | Modified: | 4 Aug 2017 14:33 |
Reporter: | monty solomon | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | CPU Architecture: | Any | |
Tags: | 5.7 |
[3 Aug 2017 21:51]
monty solomon
[3 Aug 2017 22:05]
MySQL Verification Team
miguel@ural:~ $ mysql -uroot -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 3 Server version: 5.7.19 MySQL Community Server (GPL) Copyright (c) 2000, 2017, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> SELECT @@GLOBAL.transaction_isolation, @@transaction_isolation; ERROR 1193 (HY000): Unknown system variable 'transaction_isolation' mysql> miguel@ural:~/dbs $ ./57c Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 Server version: 5.7.20 Source distribution 2017-AUG-01 Copyright (c) 2000, 2017, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql 5.7 > SELECT @@GLOBAL.transaction_isolation, @@transaction_isolation; +--------------------------------+-------------------------+ | @@GLOBAL.transaction_isolation | @@transaction_isolation | +--------------------------------+-------------------------+ | REPEATABLE-READ | REPEATABLE-READ | +--------------------------------+-------------------------+ 1 row in set (0.01 sec) mysql 5.7 >
[4 Aug 2017 6:22]
MySQL Verification Team
Thank you for the feedback.
[4 Aug 2017 14:33]
Stefan Hinz
Posted by developer: There are 2 requests here: 1) Don't release doc updates for future releases. 2) Provide separate examples for 5.7.20 and previous versions to make it easy to copy/paste to use them. Ad 1) The continuous publication policy has been in place ever since MySQL existed. We deliberately document new features or changes in upcoming releases so that people are aware ahead of time. Ad 2) Providing separate examples (in this case, for the behavior up to 5.7.19 and the new one from 5.7.20) can be beneficial, but in this particular case it's not. It would just make the documentation harder to read. Denying to make any changes because of the reasons given, and closing this bug.