-
Notifications
You must be signed in to change notification settings - Fork 177
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
Method maybe_single
errors when there are no results
#511
Comments
Hey, Thanks for filing the error! This should be fixed once corresponding Postgrest-py upgrade is merged into this branch. Let us know if this is not the case. Will leave the issue open until we bump the version and test the fix. You should be able to manually override/bump the postgrest-py version before then if needed though |
Closing as there was no reply from OP. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The
maybe_single
method seems to work when there is a single record in the database matching the query, but if there are no matching results in the database, an error is raised.To Reproduce
An example of a query is:
If there is a record with the
id
of 31, the record is returned.If there is not, an exception is raised.
The exception is as below:
Expected behavior
I expected that when there were no results,
response.data
would beNone
and no exception would be thrown.The text was updated successfully, but these errors were encountered: