Bug #36866 | Transactions and invalid sequence and no errors | ||
---|---|---|---|
Submitted: | 21 May 2008 23:45 | Modified: | 22 May 2008 20:13 |
Reporter: | Juha Vehnia | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: General | Severity: | S4 (Feature request) |
Version: | 5.0.22, 4.1, 5.0, 5.1, 6.0 BK | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | innodb, no errors, savepoint, transaction |
[21 May 2008 23:45]
Juha Vehnia
[22 May 2008 4:26]
Valeriy Kravchuk
Thank you for a problem report. Please, send the results of select @@autocommit; from your testing environment.
[22 May 2008 17:48]
Juha Vehnia
select @@autocommit returns 1
[22 May 2008 19:08]
Ken Jacobs
This would not seem to be InnoDB specific (at least once there are other transactional engines). The checks requested could be/should be done at the MySQL level and apply to all (transactional) engines. This also seems like a feature request, not an S2 problem ...
[22 May 2008 20:13]
Sveta Smirnova
Thank you for the report. Verified as described.
[2 Oct 2008 21:14]
Konstantin Osipov
Triage: risk assessment depends on the fix. If we simply return a warning, it's fairly low. If we prohibit it, as requested in the bug report and prescribed by the standard, it's an incompatible change. See also feature request in Bug#6861
[2 Oct 2008 21:15]
Konstantin Osipov
In any case, this is documented.