Changes between Initial Version and Version 2 of Ticket #10397


Ignore:
Timestamp:
03/05/09 17:38:26 (6 years ago)
Author:
jbronn
Comment:

which is used by, at a minimum, the auth tests

It's also used by any unit test that subclasses django.test.TestCase. The attached patch adds this setting; MySQL and Oracle shouldn't be affected because it's only PostGIS that really uses something different than the default connection.creation.create_test_db.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10397

    • Property Status changed from new to assigned
    • Property Cc Almad added
    • Property Patch needs improvement unset
    • Property Needs tests unset
    • Property Keywords create_spatial_db gis tests added
    • Property Milestone changed from to 1.1
    • Property Owner changed from nobody to jbronn
    • Property Needs documentation unset
    • Property Has patch set
  • Ticket #10397 – Description

    initial v2  
    1 After r9756, it's no longer possible to run a full test suite for a set of applications (a Django "project") when using the gis test runner. This is because we need to set up DATABASE_SUPPORTS_TRANSACTIONS, which is used by, at a minimum, the auth tests.
     1After r9756, it's no longer possible to run a full test suite for a set of applications (a Django "project") when using the gis test runner. This is because we need to set up `DATABASE_SUPPORTS_TRANSACTIONS`, which is used by, at a minimum, the auth tests.
    22
    33This seems like the tip of the iceberg in some ways, though. There's already a handy function to help with this, but it's part of `django.db.backends.creation.BaseDatabaseCreation`, which `django.contrib.gis` doesn't use at all for creating test databases. I suspect the solution is to break up the `BaseDatabaseCreation` class into basic stuff and test stuff so that gis can use the subclass the latter.
Back to Top