Hypertables support all standard PostgreSQL constraint types, with the exception of foreign key constraints on other tables that reference values in a hypertable. Creating, deleting, or altering constraints on hypertables will propagate to chunks, accounting also for any indexes associated with the constraints. For instance, a table can be created as follows:
CREATE TABLE conditions ( time TIMESTAMPTZ temp FLOAT NOT NULL, device_id INTEGER CHECK (device_id > 0), location INTEGER REFERENCES locations (id), PRIMARY KEY(time, device_id) ); SELECT create_hypertable('conditions', 'time');
This table will only allow positive device IDs, non-null temperature
readings, and will guarantee unique time values for each device. It
also references values in another
locations table via a foreign key
constraint. Note that time columns used for partitioning do not allow
NULL values by default. TimescaleDB will automatically add a
NULL constraint to such columns if missing.
For additional information on how to manage constraints, see the PostgreSQL docs.
Found an issue on this page?Report an issue!