Changes between Version 1 and Version 2 of Ticket #3615, comment 34


Ignore:
Timestamp:
Jun 30, 2011, 4:41:46 AM (13 years ago)
Author:
Ramiro Morales

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3615, comment 34

    v1 v2  
    33I've tried the v5 patch against sqlite3 and it creates/uncovers a bunch and errors and failures in our test suite.
    44
    5 Also, it makes the errors like the following one to be reported when loading certain `regressiontests/admin_views` fixtures (admin-views-books.xml) but they don't cause the test cases to fail. The traceback isn't very useful:
     5Also, it makes errors like the following one to be reported when loading certain `regressiontests/admin_views` fixtures (admin-views-books.xml) but they don't cause the test cases to fail. The traceback isn't very useful:
    66{{{
    77Problem installing fixture 'tests/regressiontests/admin_views/fixtures/admin-views-books.xml': Traceback (most recent call last):
    … …  
    2727To reproduce, run the `admin_views` tests, all the tests methods from `CustomModelAdminTest` suffer from this (--verbosity 2 helps to see that). The !IntegrityError's appear only when `check_constraints()` is run.
    2828
    29 Some tickets I've found that are related to this (some of them very tangentially): #14204, #15933, #16026, #8317.
     29Some tickets I've found that are related to this (some of them very tangentially): #14204, #16026, #8317, #15933.
    3030
    3131Perhaps efforts in this ticket can be focused only on enhancing the situation of tests with MySQL (i.e. move back the new sql code checks in `check_constraints()` to the `mysql` backend) and leaving the other backend alone for now?
Back to Top