#16809: MySQL is not SQL standards compliant regarding IS NULL criteria on
newly-
inserted auto-incremented fields
-------------------------------------+-------------------------------------
Reporter: jamesp | Owner: nobody
Type: Bug | Status: closed
Milestone: | Component: Database layer
Version: 1.3 | (models, ORM)
Resolution: fixed | Severity: Normal
Triage Stage: Ready for | Keywords: mysql, sql
checkin | standards, auto_increment, count
Needs documentation: 0 | Has patch: 1
Patch needs improvement: 0 | Needs tests: 0
UI/UX: 0 | Easy pickings: 0
-------------------------------------+-------------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => fixed
Comment:
In [16785]:
{{{
#!CommitTicketReference repository="" revision="16785"
Fixed #16809 -- Forced MySQL to behave like a database. This avoids a
problem where queries that do IS NONE checks can return the wrong result
the first time they are executed if there is a recently inserted row.
Thanks to James Pyrich for the debug work and patch.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16809#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
