Opened 11 years ago
Closed 11 years ago
#21779 closed Bug (invalid)
Wrong default on isolation level in queryset documentation
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Documentation | Version: | 1.6 |
Severity: | Normal | Keywords: | isolation level |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Hi Django folks,
https://docs.djangoproject.com/en/1.6/ref/models/querysets/ says that "If you are using MySQL, be sure to use the READ COMMITTED isolation level rather than REPEATABLE READ (the default)" while https://docs.djangoproject.com/en/1.6/ref/databases/#isolation-level says that "READ COMMITTED" is the default.
I think this changed with the 1.6 version and that the first link did not get updated.
Thanks,
Guillaume
Note:
See TracTickets
for help on using tickets.
Hi,
The two links are talking about different databases: he default isolation level for mysql is
REPEATABLE READ
(1st link) while it'sREAD COMMITED
for postgresql (2nd link).