Some checks failed
CI / Run lints and checks (push) Failing after 47s
CI / Run tests (push) Failing after 1s
CI / Run race tests (push) Failing after 5s
CI / Build CLI docs (push) Has been skipped
CI / Run buf actions (push) Failing after 5s
CodeQL / Analyze (go) (push) Failing after 3s
CodeQL / Analyze (javascript) (push) Failing after 2s
Docker Image Scanners / scanners (push) Failing after 3s
Format / format (push) Failing after 3s
Synchronize Issue Labels / Synchronize Issue Labels (push) Has been skipped
CI / Generate release (push) Has been skipped
CI / Draft newsletter (push) Has been skipped
CI / Pending approval Slack notification (push) Has been skipped
CI / Send newsletter (push) Has been skipped
25 lines
1.1 KiB
SQL
25 lines
1.1 KiB
SQL
-- we can not fizz this migration because there is no check constraint support in fizz
|
|
-- and it gets cumbersome with sqlite; having a working SQL version is actually way easier
|
|
CREATE TABLE keto_relation_tuples
|
|
(
|
|
shard_id UUID NOT NULL,
|
|
nid UUID NOT NULL,
|
|
namespace_id INTEGER NOT NULL,
|
|
object VARCHAR(64) NOT NULL,
|
|
relation VARCHAR(64) NOT NULL,
|
|
subject_id VARCHAR(64) NULL,
|
|
subject_set_namespace_id INTEGER NULL,
|
|
subject_set_object VARCHAR(64) NULL,
|
|
subject_set_relation VARCHAR(64) NULL,
|
|
commit_time TIMESTAMP NOT NULL,
|
|
|
|
PRIMARY KEY (shard_id, nid),
|
|
|
|
-- enforce to have exactly one of subject_id or subject_set
|
|
CONSTRAINT chk_keto_rt_subject_type CHECK
|
|
((subject_id IS NULL AND
|
|
subject_set_namespace_id IS NOT NULL AND subject_set_object IS NOT NULL AND subject_set_relation IS NOT NULL)
|
|
OR
|
|
(subject_id IS NOT NULL AND
|
|
subject_set_namespace_id IS NULL AND subject_set_object IS NULL AND subject_set_relation IS NULL))
|
|
); |