Bug #10868 | select ... for update broken for max() and perhaps other aggregates | ||
---|---|---|---|
Submitted: | 25 May 2005 21:06 | Modified: | 8 Aug 2007 9:43 |
Reporter: | John Muehlhausen | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S1 (Critical) |
Version: | 4.1.12 | OS: | Any (OS 10.3.9) |
Assigned to: | CPU Architecture: | Any |
[25 May 2005 21:06]
John Muehlhausen
[29 May 2005 20:07]
Martin Skold
This either requires a table lock or a consistent read for a non-blocking implementation of highest transaction isolation level, serializable. Both are feature requests and will be done later.
[4 Oct 2006 17:17]
John Muehlhausen
Is there any update on this issue?
[7 Oct 2006 9:47]
Stewart Smith
SELECT ... FOR UPDATE for NDB was fixed in a recent release - check the release notes in the manual.
[8 Aug 2007 9:43]
Hartmut Holzgraefe
duplicate, original bug got fixed