#16054: Unexpected DB Caching Behaviour with MySQL
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
brendoncrawford | Status: closed
Type: Bug | Component: Database layer
Milestone: | (models, ORM)
Version: 1.3 | Severity: Normal
Resolution: invalid | Keywords:
Triage Stage: | Has patch: 0
Unreviewed | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Changes (by russellm):
* status: new => closed
* needs_docs: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
This is a normal and expected behavior for certain transaction isolation
modes. [http://dev.mysql.com/doc/refman/5.0/en/set-transaction.html See
the MySQL docs on transaction isolation modes] for more details, or ask on
django-users.
--
Ticket URL: <https://code.djangoproject.com/ticket/16054#comment:1>
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.