Skip to content

D
django
Dal (branch)/etiket değiştir
  1. 06 Şub, 2015 1 kayıt (commit)
  3. 22 Mar, 2014 1 kayıt (commit)
  5. 21 Mar, 2014 1 kayıt (commit)
  7. 03 Kas, 2013 1 kayıt (commit)
  9. 26 Eki, 2013 1 kayıt (commit)
  11. 23 Eki, 2013 1 kayıt (commit)
  13. 18 Eki, 2013 1 kayıt (commit)
  15. 08 Eyl, 2013 1 kayıt (commit)
  17. 29 Tem, 2013 1 kayıt (commit)
  19. 10 Haz, 2013 1 kayıt (commit)
  21. 11 Mar, 2013 1 kayıt (commit)
    • Aymeric Augustin's avatar
      Made transaction.managed a no-op and deprecated it. · 7aacde84
      Aymeric Augustin yazdı 
      enter_transaction_management() was nearly always followed by managed().

In three places it wasn't, but they will all be refactored eventually.
The "forced" keyword argument avoids introducing behavior changes until
then.

This is mostly backwards-compatible, except, of course, for managed
itself. There's a minor difference in _enter_transaction_management:
the top self.transaction_state now contains the new 'managed' state
rather than the previous one. Django doesn't access
self.transaction_state in _enter_transaction_management.
      7aacde84
  23. 27 Şub, 2013 1 kayıt (commit)
    • Anssi Kääriäinen's avatar
      Fixed #19861 -- Transaction ._dirty flag improvement · 50328f0a
      Anssi Kääriäinen yazdı 
      There were a couple of errors in ._dirty flag handling:
  * It started as None, but was never reset to None.
  * The _dirty flag was sometimes used to indicate if the connection
    was inside transaction management, but this was not done
    consistently. This also meant the flag had three separate values.
  * The None value had a special meaning, causing for example inability
    to commit() on new connection unless enter/leave tx management was
    done.
  * The _dirty was tracking "connection in transaction" state, but only
    in managed transactions.
  * Some tests never reset the transaction state of the used connection.
  * And some additional less important changes.

This commit has some potential for regressions, but as the above list
shows, the current situation isn't perfect either.
      50328f0a
  25. 26 Şub, 2013 1 kayıt (commit)
  27. 10 Şub, 2013 1 kayıt (commit)
    • Anssi Kääriäinen's avatar
      Fixed #19720 -- Oracle ordering related delete regression · 8ef32350
      Anssi Kääriäinen yazdı 
      When a query had a complex where condition (a condition targeting more
than the base table) a subquery was used for deletion. However, the
query had default ordering from the model's meta and Oracle doesn't
work with ordered subqueries.

The regression was caused by fast-path deletion code introduced in
1cd6e04c for fixing #18676.

Thanks to Dylan Klomparens for the report.
      8ef32350
  29. 27 Kas, 2012 1 kayıt (commit)
  31. 25 Eki, 2012 2 kayıt (commit)
  33. 28 Eyl, 2012 1 kayıt (commit)
    • Anssi Kääriäinen's avatar
      Fixed #18676 -- Allow fast-path deletion of objects · 1cd6e04c
      Anssi Kääriäinen yazdı 
      Objects can be fast-path deleted if there are no signals, and there are
no further cascades. If fast-path is taken, the objects do not need to
be loaded into memory before deletion.

Thanks to Jeremy Dunck, Simon Charette and Alex Gaynor for reviewing
the patch.
      1cd6e04c
  35. 17 Mar, 2012 1 kayıt (commit)
  37. 16 Mar, 2012 1 kayıt (commit)
  39. 12 Mar, 2012 1 kayıt (commit)
  41. 05 Mar, 2012 1 kayıt (commit)
  43. 13 Eki, 2011 1 kayıt (commit)
  45. 13 Tem, 2011 1 kayıt (commit)
  47. 10 Haz, 2011 1 kayıt (commit)
  49. 30 May, 2011 1 kayıt (commit)
  51. 03 Mar, 2011 1 kayıt (commit)
  53. 12 Şub, 2011 1 kayıt (commit)
  55. 25 Ock, 2011 1 kayıt (commit)
  57. 19 Ock, 2011 1 kayıt (commit)
  59. 11 Eki, 2010 1 kayıt (commit)
  61. 09 Nis, 2010 1 kayıt (commit)
  63. 15 Mar, 2010 1 kayıt (commit)