Changes between Initial Version and Version 1 of Ticket #23879, comment 5


Ignore:
Timestamp:
Dec 1, 2014, 4:51:27 AM (10 years ago)
Author:
Wojtek Ruszczewski

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #23879, comment 5

    initial v1  
    11I can confirm that removing the GIS toggle already gives a bunch of skipped tests without any failures or errors.
    22
    3 On the other hand, postgres tests can't be dealt with easily -- `postgres_tests` have some migrations that rely on PostgreSQL specific operations, and cause the test database creation to fail with any other backend. Resolving this would require some way to limit migrations or whole test apps to specific backends.
     3On the other hand, postgres tests can't be skipped that easily -- `postgres_tests` has some migrations that rely on PostgreSQL specific operations and cause the test database creation to fail with any other backend.
    44
    5 I was able to get it to work with an [https://github.com/wrwrwr/django/compare/feature/always-test-gis-and-postgres ad-hoc solution] (that wasn't properly thought over or researched). It may be an interesting question how to deal with database-specific migrations in reusable apps.
     5Resolving this would probably require some way to bypass migrations or whole test apps depending on database backend / vendor. I was able to get it to work with an [https://github.com/wrwrwr/django/compare/feature/always-test-gis-and-postgres ad-hoc solution] (that hasn't been properly thought over or researched), but it may be an interesting question how to provide database-specific migrations with reusable apps.
Back to Top