mirror of
https://github.com/django/django.git
synced 2025-01-12 19:37:06 +00:00
4e9a74b81d
Thanks to Jeremy Dunck for pointing out the problem with this change. If in a
single transaction, the master deletes a record and then get_or_creates a
similar record, under the new behavior the get_or_create would find the record
in the slave db and fail to re-create it, leaving the record nonexistent, which
violates the contract of get_or_create that the record should always exist
afterwards. We need to do everything against the master here in order to ensure
correctness.
This reverts commit
|
||
---|---|---|
.. | ||
0.95.txt | ||
0.96.txt | ||
1.0-alpha-1.txt | ||
1.0-alpha-2.txt | ||
1.0-beta-2.txt | ||
1.0-beta.txt | ||
1.0-porting-guide.txt | ||
1.0.1.txt | ||
1.0.2.txt | ||
1.0.txt | ||
1.1-alpha-1.txt | ||
1.1-beta-1.txt | ||
1.1-rc-1.txt | ||
1.1.2.txt | ||
1.1.3.txt | ||
1.1.4.txt | ||
1.1.txt | ||
1.2-alpha-1.txt | ||
1.2-beta-1.txt | ||
1.2-rc-1.txt | ||
1.2.1.txt | ||
1.2.2.txt | ||
1.2.3.txt | ||
1.2.4.txt | ||
1.2.5.txt | ||
1.2.6.txt | ||
1.2.7.txt | ||
1.2.txt | ||
1.3-alpha-1.txt | ||
1.3-beta-1.txt | ||
1.3.1.txt | ||
1.3.2.txt | ||
1.3.txt | ||
1.4-alpha-1.txt | ||
1.4-beta-1.txt | ||
1.4.1.txt | ||
1.4.2.txt | ||
1.4.txt | ||
1.5.txt | ||
index.txt |