-
-
Notifications
You must be signed in to change notification settings - Fork 22
Async ORM mutations and queries #134
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
Conversation
@rmorshea I'm seeing some weird behavior that might indicate a bug with async Let me know when you have time for me to demo. |
I'll have time in an hour. |
Ops forgot to add async mutation support... EDIT: Past me apparently already semi-developed it, but I'm not sure what direction to take for a |
Regarding a
|
This PR is ready for review. I did a tabletop self-review and cleaned up a couple things. |
Will try to find time. Going to be quite busy the next two weeks. |
I played around with the test to get things running faster and more reliably. |
@rmorshea Can we schedule a review for this one? |
Description
fix #135
thread_sensitive
where it's not neededuse_query
now supports async functions.use_mutation
now supports async functions.django_idom.types.QueryOptions.thread_sensitive
option to customize how sync queries are executed.django_idom.hooks.use_mutation
now acceptsdjango_idom.types.MutationOptions
option to customize how mutations are executed.kwarg
andargs
. This allow things such asquery=my_function
to be properly handled.mutate
argument ondjango_idom.hooks.use_mutation
has been renamed tomutation
.Checklist:
Please update this checklist as you complete each item: