diff options
| author | Alex <acbecker@uchicago.edu> | 2019-05-17 03:23:10 -0700 |
|---|---|---|
| committer | Carlton Gibson <carlton.gibson@noumenal.es> | 2019-05-17 12:25:12 +0200 |
| commit | 4ef96cce6a7ab302227ab3df0b57179e1c392c3c (patch) | |
| tree | a9a22d3c059b46a7b59776d8093d129a14f2a942 /docs/ref/databases.txt | |
| parent | 34a357d519a6ff37516c963181af912f776ea80d (diff) | |
[2.2.x] Fixed #30199 -- Adjusted QuerySet.get_or_create() docs to highlight atomicity warning.
Backport of 1686dce06c1f3587e90ea98816eddaa965fd9f45 from master
Diffstat (limited to 'docs/ref/databases.txt')
| -rw-r--r-- | docs/ref/databases.txt | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 05ea7d2e74..84dce9fa7c 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -488,7 +488,10 @@ this entry are the four standard isolation levels: or ``None`` to use the server's configured isolation level. However, Django works best with and defaults to read committed rather than MySQL's default, -repeatable read. Data loss is possible with repeatable read. +repeatable read. Data loss is possible with repeatable read. In particular, +you may see cases where :meth:`~django.db.models.query.QuerySet.get_or_create` +will raise an :exc:`~django.db.IntegrityError` but the object won't appear in +a subsequent :meth:`~django.db.models.query.QuerySet.get` call. .. _transaction isolation level: https://dev.mysql.com/doc/refman/en/innodb-transaction-isolation-levels.html |