-
-
Notifications
You must be signed in to change notification settings - Fork 677
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
.execute_write(... block=True)
should be the default behaviour
#1579
Comments
This is technically a breaking change, but a GitHub code search at https://cs.github.com/?scopeName=All+repos&scope=&q=execute_write%20datasette%20-owner%3Asimonw shows only one repo not-owned-by-me using this, and they're using |
The easiest way to change this would be to default to An alternative would be to add new, separately named methods which do the fire-and-forget thing. If I hadn't recently added |
I'm going to go with |
Re-opening this because I missed updating some of the docs, and I also need to update Datasette's own code to not use |
Updated docs for |
All of those removed |
Every single piece of code I've written against the write APIs has used the
block=True
option to wait for the result.Without that, it instead fires the write into the queue but then continues even before it has finished executing.
block=True
should clearly be the default behaviour here!The text was updated successfully, but these errors were encountered: