Changes between Initial Version and Version 1 of Ticket #26347, comment 14


Ignore:
Timestamp:
03/16/16 23:13:37 (4 years ago)
Author:
Shai Berger
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #26347, comment 14

    initial v1  
    55Further, per Django's contribution guide, please do not re-open a ticket that was marked "wontfix" by a core developer; you should bring it up on the DevelopersMailingList. Tim has already started a [https://groups.google.com/d/msgid/django-developers/286b0efb-673f-42d7-a1f3-5de76fc039c5%40googlegroups.com thread] for it that you might join.
    66
    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)
Back to Top