Skip to content

thoughts on data validation rules on write #387

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
+13 −0
Draft

thoughts on data validation rules on write #387

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
13 changes: 13 additions & 0 deletions notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,16 @@
# write permissions

- 2 phase commit
- whole row to write callback
- write callback can reject in which case we..
Well no data changed but we need to get the data back to the client.
We could
1. record the db version that failed and somehow get that back to the client
2. bump the db version of the record, causing all clients to re-pull it
3. Do nothing an allow client to be diverged.

Note: data validation rules / write permissions should only be enforced in a hub and spoke topology.

# back-to-cid

- cid from `pragma_table_info`
Expand Down