"Mike Bayer" <mike...@zzzcomputing.com> writes: > a fix for that is coming through at > https://github.com/sqlalchemy/sqlalchemy/issues/7979 > > though it's best to give types to bindparam() objects if they don't have a > value
Thank you Mike, and sorry for not providing a MWE of my issue in my first post. I confirm that explicitly typing the bind parameters fixed the issue. W.r.t. > (do you really need to use bindparam() directly?) well, yes, it's very handy in this case, because as said this is a moderately complex query, dinamically composed by several different smaller "chunks" generated by common functions, used in several other places. It would be very impractical to carry around the whole set of "parameters" and use the implicit/automatic injection made by SA. Thanks again, ciao, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. l...@metapensiero.it | -- Fortunato Depero, 1929. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ 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 view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/878rrjgjaj.fsf%40metapensiero.it.
