-
Notifications
You must be signed in to change notification settings - Fork 15
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.
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
[NEW] Bulk Delete Workaround #25
Comments
Transactions can be used for bulk deletion. "Transactions are used when deleting multiple records:” which is documented for delete, but can make this clearer |
I think for this scenario, SQL is the best answer |
Had a conversation with @SferaDev. The SQL proxy limitation for this is a backend issue. Suggesting the following SQL based on Alexis and Kostas (suggestion in Discord)
|
Closes #25 #42 ## Summary <!-- Add a brief description of changes --> - **Adding examples and timeout note** - Adding examples to the transactions doc and clarifying language. Also including the timeout that occurs with bulk deletes mentioned in [Discord](https://discord.com/channels/996791218879086662/1075788625586966637/threads/1201746322370342952) --- <!-- Remove this entire section if not needed --> ### Remaining work The following work still needs to be completed: - [ ] <List outstanding tasks here> ### Dependencies - [ ] <Tasks that must be completed before merging this pull request> --- ### Timing **Release**: - [ ] When ready - [ ] Hold for release | Release after: <mm/dd/yy> --------- Co-authored-by: Philip Krauss <35487337+philkra@users.noreply.github.com> Co-authored-by: Kostas Botsas <kostas@xata.io>
Feedback
Would like to see an example of deleting all rows matching a specific criteria. That could also include matching against linked data. If that is possible?
Workaround for now filter out all ids matching a linked column and then make multiple calls to delete. Just felt a bit inefficient :)
Route
https://xata.io/docs/api-guide/delete
From
lindgr3n
Original issue: https://github.com/xataio/docs/issues/82
The text was updated successfully, but these errors were encountered: