I’m currently using timescaledb to model trades and quotes. In our system, many trades can be associated with many quotes and vice versa, which leads to a many-to-many relationship.
Our trades table is a hypertable while our quotes table is just a regular table. Unfortunately, since timescaledb does not support foreign keys, it makes creating a junction table quite difficult (and the application needs to enforce the foreign key constraint).
I’m wondering what options there are for modelling many-to-many relationships in timescaledb and what the tradeoffs are. Thanks!