-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
new stack trace when combining non-eq compare_values w/ SQL expression in ORM persist #3402
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
Michael Bayer (@zzzeek) wrote: well if we have a SQL expression we know it has to be run, so in that case we skip the comparison. Confirm this is what 0.9 is doing and add a test to test_unitofworkv2:
|
Michael Bayer (@zzzeek) wrote: Here's the test case using something much more normal, occurs with boolean expressions, as the operator comes out as "is_()":
we might want to consider "is" and "isnot" OK for the |
Michael Bayer (@zzzeek) wrote:
→ b0be921 |
Changes by Michael Bayer (@zzzeek):
|
Migrated issue, originally created by Michael Bayer (@zzzeek)
this is a 1.0 regression, though I'm pretty curious to see what 0.9 is doing that it isn't hitting this exception:
The text was updated successfully, but these errors were encountered: