I am trying to use a composite primary key in postgres with Django/TimescaleDB (composite keys are new since Django 5.2). During the creation of the timescale hypertables, however, the primary key is automatically dropped by django-timescaledb (_drop_primary_key) just before the hypertable creation. Is there a workaround for this, or is this drop still required?
I am trying to use a composite primary key in postgres with Django/TimescaleDB (composite keys are new since Django 5.2). During the creation of the timescale hypertables, however, the primary key is automatically dropped by django-timescaledb (_drop_primary_key) just before the hypertable creation. Is there a workaround for this, or is this drop still required?