Are the hypertables effectively views with insert triggers on them?
Does Timescale have any baked in support bitemporal constructs?
Are temporal foreign keys supported?
Does Timescale have any baked in support bitemporal constructs?
Are temporal foreign keys supported?
We do not currently support bitemporal constructs.
What's an example of a temporal foreign key query that you need?
Basically, does the database have an opinion on time oriented data consistency?
We are not really built for that use case. Instead of focusing on fundamentally relational data such as people or jobs (which you are free to store alongside our stuff, using plain postgres functionality), we store event or metrics data. This data can be easily joined against the relational data (e.g., using a person_id stored in both event and relational tables).
That makes sense, thanks for answering ;)