Changes between Initial Version and Version 1 of Ticket #34456
- Timestamp:
- Apr 4, 2023, 7:41:14 AM (20 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #34456 – Description
initial v1 1 We use [django-timescaledb](https://github.com/schlunsen/django-timescaledb)as our database backend and ran into a problem with some of our tests for django migrations on tables using timescale compression.1 We use https://github.com/schlunsen/django-timescaledb as our database backend and ran into a problem with some of our tests for django migrations on tables using timescale compression. 2 2 3 I [wrote up our problem on `django-timescaledb` back in October ](https://github.com/schlunsen/django-timescaledb/issues/40),but it essentially boils down to:3 I [wrote up our problem on `django-timescaledb` back in October (https://github.com/schlunsen/django-timescaledb/issues/40) but it essentially boils down to: 4 4 5 5 * `django.test.testcases.TransactionTestCase._fixture_teardown()` calls `django.db.backends.postgresql.operations.sql_flush()` and truncates every table at the end of tests.