On Monday, October 17, 2016 at 3:58:36 PM UTC-4, Mike Bayer wrote:
> that error is there right now because we don't emit the "col IS NULL" 
> SQL within that section of the persistence code. 
> took me a long time to find the history on this because I thought it had 
> been discussed but looks like the answer was "no immediate plans": 
> https://bitbucket.org/zzzeek/sqlalchemy/issues/2127#comment-9011753 
> that is, we can't just drop that assertion without adding logic to alter 
> the SQL for some parameters. 
I see. Makes sense. Thanks.

SQLAlchemy - 
The Python SQL Toolkit and Object Relational Mapper


To post example code, please provide an MCVE: Minimal, Complete, and Verifiable 
Example.  See  http://stackoverflow.com/help/mcve for a full description.
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

Reply via email to