-
Notifications
You must be signed in to change notification settings - Fork 30
Postgrest - Where filter with nullable field doesn't work #61
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
Comments
Great report as always. Fixed in 3.1.2! |
thank you! |
Hi, just another catch. This time it isn't breaking my code, but I take the liberty of informing. 🥲 If the right side of the predicate is a variable defined as nullable, it throws the following exception.
|
@rhuanbarros Could you show me the model you're working with on that? |
Sorry for the delay.
If int ListaId is defined as int? ListaId, it throws that exception. |
@rhuanbarros Can you try this on the latest version? |
Hi, I was on a little vacation last week. Soon I will take a look in it. |
No rush friend - Hope it was a good vacation! |
I tried with the latest version, it threw the same exception, but I figured out that I messed up my code. |
This issue is happening again in postgres 4.0.3 model:
|
Bug report
Describe the bug
A call to the database using Where or Filter method with a nullable field throws the following exception:
If the field is not nullable it works fine.
To Reproduce
Example:
CreatedAt is defined as:
Expected behavior
Filter as it already works with a not nullable field.
Project information
The text was updated successfully, but these errors were encountered: