diff options
| author | Carl Meyer <carl@oddbird.net> | 2012-09-19 11:15:12 -0600 |
|---|---|---|
| committer | Carl Meyer <carl@oddbird.net> | 2012-09-19 11:15:12 -0600 |
| commit | 4e9a74b81df1c7aaea2f90a3a4911920e134b275 (patch) | |
| tree | c13560e59eb490a936c854cc92b83627d2477b89 /docs | |
| parent | 901af865505310a70dd02ea5b3becbf45819b652 (diff) | |
Revert "Fixed #16865 -- Made get_or_create use read database for initial get query."
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 901af865505310a70dd02ea5b3becbf45819b652.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/1.5.txt | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/docs/releases/1.5.txt b/docs/releases/1.5.txt index 84c37af9ee..26b6ad1bfa 100644 --- a/docs/releases/1.5.txt +++ b/docs/releases/1.5.txt @@ -338,15 +338,6 @@ Miscellaneous needs. The new default value is `0666` (octal) and the current umask value is first masked out. -* In a multi-database situation, ``get_or_create()`` will now use a read - database for the initial ``get`` attempt (previously, it used only the write - database for all queries). This change reduces load on the write (master) - database, in exchange for slightly more frequent false-negatives on the - initial ``get`` due to replication lag. In those cases the subsequent insert - will still go to the master and fail, after which the existing object will be - fetched from the master. - - Features deprecated in 1.5 ========================== |