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
|
||
---|---|---|
.. | ||
modeltests | ||
regressiontests | ||
templates | ||
runtests.py | ||
test_sqlite.py | ||
urls.py |