Tutorial/cascade delete #70
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
December 24, 2024 12:38
benitav
reviewed
Dec 24, 2024
| ``` | ||
|
|
||
| <Note> | ||
| An important thing to note is that the local SQLite database will always match the online database, as long as the tables are in the publication, when online. |
There was a problem hiding this comment.
"online database" is a bit confusing - can we say backend database to be more consistent with how we refer to it across docs?
benitav
reviewed
Dec 24, 2024
|
|
||
| <Note> | ||
| An important thing to note is that the local SQLite database will always match the online database, as long as the tables are in the publication, when online. | ||
| For example, if you delete a record from the `lists` table and Supabase cascade deletes a record from the `todo` table, PowerSync will also delete the `todo` record when online. |
There was a problem hiding this comment.
Worth explicitly saying "local lists table" and "local todo record" if that's correct. Basically make clear when we're taking about records in the SQLite database vs backend database
benitav
reviewed
Dec 24, 2024
| </Note> | ||
| 2. Implementing triggers (which is more complex) | ||
| <Note> | ||
| You create triggers on the internal tables (not the views defined by the client schema), similar to what is |
There was a problem hiding this comment.
Maybe worth linking to https://docs.powersync.com/architecture/client-architecture#schema so they can get more details about the internal tables vs views thing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a tutorial that shows how to perform a cascading delete on the client.