tickets: 8792
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8792 | 2008-09-02 09:56:47 | 2009-03-01 12:13:57 | 2022-03-06 03:43:10.945404 | Unreviewed | closed | Testing framework | dev | wontfix | Django's unit test system wipes out "custom sql" data before performing tests | Django's unit test system issues "flush" command (resulting in a truncate for all tables) just before performing tests. This causes problems when having custom sql scripts (<appname>/sql/<modelname>.sql) because all this data is wiped out by the truncate and might be required for the tests. Django's test execution path: - tables creation - custom sql execution (potential data insertion) - flush (truncate all tables) - perform tests (without potential custom sql data!) I think it might be good to execute custom sql after the truncate has occurred ... | nobody | deltoide | 0 | 0 | 0 | 0 | 0 | 0 |