We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Is your feature request related to a problem? Please describe.
STR (in the dev env):
sqlite3
delete from users;
Expected result: inbox is empty.
Actual result: inbox shows previous message
Why? Step 3 allows deleting rows from the users table when the foreign keys should prevent that (or should cascade to delete related rows).
users
Describe the solution you'd like
Within SQLite, we can enable the foreign_key_check pragma.
foreign_key_check
Ideally we should just switch to Postgres across the board as per #557
Additional context
This only affects the dev and test environments.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe.
STR (in the dev env):
sqlite3
CLI withdelete from users;
Expected result: inbox is empty.
Actual result: inbox shows previous message
Why? Step 3 allows deleting rows from the
users
table when the foreign keys should prevent that (or should cascade to delete related rows).Describe the solution you'd like
Within SQLite, we can enable the
foreign_key_check
pragma.Ideally we should just switch to Postgres across the board as per #557
Additional context
This only affects the dev and test environments.
The text was updated successfully, but these errors were encountered: