Skip to content

fix: Fix old migrations for Keto 0.8, column nit is not exists in table network #1573

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DarkDrim wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix: Fix old migrations for Keto 0.8, column nit is not exists in table network #1573

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion internal/persistence/sql/migrations/sql/20220217152313000000_nid_fk.sqlite.up.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
-- These tuples can't be retrieved over any API (and also not inserted by any API) because we always add a `WHERE nid = ?` clause to the queries.
-- This DELETE statement is here to ensure that we don't run into problems where the `nid` column is not properly set. Should not happen if only the official API is used.
DELETE FROM keto_relation_tuples WHERE nid NOT IN (SELECT nid FROM networks);
DELETE FROM keto_relation_tuples WHERE nid NOT IN (SELECT id FROM networks);

CREATE TABLE keto_relation_tuples_with_fk
(
Expand Down
2 changes: 1 addition & 1 deletion internal/persistence/sql/migrations/sql/20220217152313000000_nid_fk.up.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
-- These tuples can't be retrieved over any API (and also not inserted by any API) because we always add a `WHERE nid = ?` clause to the queries.
-- This DELETE statement is here to ensure that we don't run into problems where the `nid` column is not properly set. Should not happen if only the official API is used.
DELETE FROM keto_relation_tuples WHERE nid NOT IN (SELECT nid FROM networks);
DELETE FROM keto_relation_tuples WHERE nid NOT IN (SELECT id FROM networks);

ALTER TABLE keto_relation_tuples
ADD CONSTRAINT keto_relation_tuples_nid_fk
Expand Down