Bug #34833 | repeatable is not documented as a valid tx_isolation level | ||
---|---|---|---|
Submitted: | 26 Feb 2008 12:43 | Modified: | 18 Apr 2008 16:26 |
Reporter: | Rizwan Maredia | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.1.22 | OS: | Windows |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
Tags: | repeatable, REPEATABLE-READ, tx_isolation |
[26 Feb 2008 12:43]
Rizwan Maredia
[26 Feb 2008 14:26]
Valeriy Kravchuk
Thank you for a problem report. I agree that if this is intended behaviour the following pages: http://dev.mysql.com/doc/refman/5.0/en/innodb-transaction-isolation.html http://dev.mysql.com/doc/refman/5./en/innodb-transaction-isolation.html should be updated.
[18 Apr 2008 16:26]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products. REPEATABLE is not an alias for REPEATABLE-READ. It turns out that what's going on here is that the value can be set using any unique prefix of a valid value. The same is also true for query_cache_type and myisam_stats_method.