| 7 | | (actually, having looked at the related ticket, there is a one-line change that would probably work around the problem for Django's use: Change https://github.com/django/django/blob/1.8.11/django/db/models/fields/related.py#L1090 from `}))` to `}).for_update())`. You are welcome to try it, and a patch for that may even be accepted for 1.8 if it indeed helps to prevent a data-loss. MySql's behavior where updates see different data than selects is still unacceptable) |
| | 7 | (actually, having looked at the related ticket, there is a one-line change that would probably work around the problem for Django's use: Change https://github.com/django/django/blob/1.8.11/django/db/models/fields/related.py#L1089 from `}))` to `}).for_update())`. You are welcome to try it, and a patch for that may even be accepted for 1.8 if it indeed helps to prevent a data-loss. MySql's behavior where updates see different data than selects is still unacceptable) |
| | 8 | |
| | 9 | (edit: I had the wrong line number) |