1. 27 Agu, 2015 1 kayıt (commit)
  2. 25 Agu, 2015 1 kayıt (commit)
  3. 24 Agu, 2015 2 kayıt (commit)
    • Maxime Lorant's avatar
    • Tommy Beadle's avatar
      Fixed #23727 -- Inhibited the post_migrate signal when using serialized_rollback. · d3fdaf90
      Tommy Beadle yazdı
      When using a TransactionTestCase with serialized_rollback=True,
      after creating the database and running its migrations (along with
      emitting the post_migrate signal), the contents of the database
      are serialized to _test_serialized_contents.
      
      After the first test case, _fixture_teardown() would flush the
      tables but then the post_migrate signal would be emitted and new
      rows (with new PKs) would be created in the django_content_type
      table. Then in any subsequent test cases in a suite,
      _fixture_setup() attempts to deserialize the content of
       _test_serialized_contents, but these rows are identical to the
      rows already in the database except for their PKs.  This causes an
      IntegrityError due to the unique constraint in the
      django_content_type table.
      
      This change made it so that in the above scenario the post_migrate
      signal is not emitted after flushing the tables, since it will be
      repopulated during fixture_setup().
      d3fdaf90
  4. 15 Agu, 2015 1 kayıt (commit)
  5. 11 Agu, 2015 1 kayıt (commit)
  6. 22 Tem, 2015 1 kayıt (commit)
  7. 13 Tem, 2015 1 kayıt (commit)
    • Andrei Kulakov's avatar
      Fixed #24375 -- Added Migration.initial attribute · db97a884
      Andrei Kulakov yazdı
      The new attribute is checked when the `migrate --fake-initial` option
      is used. initial will be set to True for all initial migrations (this
      is particularly useful when initial migrations are split) as well as
      for squashed migrations.
      db97a884
  8. 03 Tem, 2015 1 kayıt (commit)
  9. 02 Tem, 2015 2 kayıt (commit)
  10. 22 Haz, 2015 1 kayıt (commit)
  11. 18 Haz, 2015 1 kayıt (commit)
  12. 17 Haz, 2015 2 kayıt (commit)
  13. 11 Haz, 2015 1 kayıt (commit)
  14. 09 Haz, 2015 1 kayıt (commit)
  15. 06 Haz, 2015 1 kayıt (commit)
  16. 05 Haz, 2015 1 kayıt (commit)
  17. 31 May, 2015 1 kayıt (commit)
  18. 19 May, 2015 1 kayıt (commit)
  19. 16 May, 2015 1 kayıt (commit)
  20. 24 Nis, 2015 1 kayıt (commit)
  21. 20 Nis, 2015 1 kayıt (commit)
  22. 13 Nis, 2015 1 kayıt (commit)
  23. 05 Nis, 2015 1 kayıt (commit)
  24. 01 Nis, 2015 1 kayıt (commit)
  25. 30 Mar, 2015 1 kayıt (commit)
  26. 27 Mar, 2015 1 kayıt (commit)
  27. 21 Mar, 2015 1 kayıt (commit)
  28. 20 Mar, 2015 1 kayıt (commit)
  29. 12 Mar, 2015 2 kayıt (commit)
  30. 05 Mar, 2015 1 kayıt (commit)
  31. 23 Şub, 2015 1 kayıt (commit)
    • Ian Lee's avatar
      Broke long lines in code examples. · 00fbd8fd
      Ian Lee yazdı
      The website only renders code blocks at 96 chars, and therefore
      long code lines get wrapped. Manually breaking the lines prevents
      the wrapping from occurring.
      00fbd8fd
  32. 09 Şub, 2015 1 kayıt (commit)
  33. 03 Şub, 2015 1 kayıt (commit)
    • Matthew Somerville's avatar
      Fixed #24240 -- Allowed GZipping a Unicode StreamingHttpResponse · 250aa7c3
      Matthew Somerville yazdı
      make_bytes() assumed that if the Content-Encoding header is set, then
      everything had already been dealt with bytes-wise, but in a streaming
      situation this was not necessarily the case.
      
      make_bytes() is only called when necessary when working with a
      StreamingHttpResponse iterable, but by that point the middleware has
      added the Content-Encoding header and thus make_bytes() tried to call
      bytes(value) (and dies). If it had been a normal HttpResponse,
      make_bytes() would have been called when the content was set, well
      before the middleware set the Content-Encoding header.
      
      This commit removes the special casing when Content-Encoding is set,
      allowing unicode strings to be encoded during the iteration before they
      are e.g. gzipped. This behaviour was added a long time ago for #4969 and
      it doesn't appear to be necessary any more, as everything is correctly
      made into bytes at the appropriate places.
      
      Two new tests, to show that supplying non-ASCII characters to a
      StreamingHttpResponse works fine normally, and when passed through the
      GZip middleware (the latter dies without the change to make_bytes()).
      Removes the test with a nonsense Content-Encoding and Unicode input - if
      this were to happen, it can still be encoded as bytes fine.
      250aa7c3
  34. 19 Ock, 2015 1 kayıt (commit)
  35. 12 Ock, 2015 1 kayıt (commit)
  36. 22 Ara, 2014 1 kayıt (commit)