-
Notifications
You must be signed in to change notification settings - Fork 30
Using LINQ expression to handle DateTime comparisons produces inconsistent results. #76
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
@wiverson do you see any obvious reason why it would be problematic to remove |
This is a deviation from how the original query worked, so it's been removed. It is incorrect to force a Now available in 3.2.10 |
Sorry I'm late, FWIW I think most ORMs would prefer deferring to the underlying datetime w/tz instead of the conversion. I wish all dbs and timestamps were UTC but alas. FWIW I'd add some test cases to cover more time/date stuff for the different db date/time configurations or at least add as a issue for later? |
Agreed! I'll add it as a chore. Thanks @wiverson! |
Referenced Lines:
postgrest-csharp/Postgrest/Linq/WhereExpressionVisitor.cs
Lines 184 to 215 in a0b36bd
Issue Report:
Re: supabase-community/supabase-csharp#121
Reproducing this issue [from @aquatyk here]
The text was updated successfully, but these errors were encountered: