We added a compount primary key using ``@@id([puckId, recordedDateTime])`` where those fields are mapped to

pb_puck_id

and `pb_recorded_timestamp`` It seemingly created the index we expected

(pb_puck_id_pb_recorded_timestamp_idx)

hoever, on each new migration, prisma attempts to drop the index. I’m pretty stumped, any ideas? Bonus: We made the table a timescaledb hypertable, which might be the issue

@William Chantry 👋 I would suggest creating a bug report with any reproduction steps so that we can look into this. It would also be great if you could add a 👍 to this request for Timescale DB so that we know the priority for this 🙂

@Ryan Thanks Ryan, I turns out Timescaledb altered the indexing when we made the table a hypertable