Changes between Initial Version and Version 1 of Ticket #32872


Ignore:
Timestamp:
Jun 21, 2021, 6:59:26 PM (3 years ago)
Author:
Tim Graham
Comment:

Django doesn't provide any support or testing for TimescaleDB, so it's not clear that Django is at fault. Feel free to reopen if you can at least provide some analysis of the situation. I imagine a custom database backend might be required which should be done as a third-party package rather than in Django itself.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #32872

    • Property Resolution → needsinfo
    • Property Status new → closed

  • Ticket #32872 – Description

    initial v1  
    11If you use a TimescaleDB and run your unit tests in parallel Django will fail to clone the first test database to the additional databases.
    2 
     2{{{
    33Cloning test database for alias 'foo' ('foo_testDB')...Got an error creating the test database: source database "foo_testDB" is being accessed by other users
    44DETAIL: There is 1 other session using the database.
    … …  
    2121#### Test call
    2222python manage.py test --parallel 4
     23}}}
Back to Top