that’s kind of awful, and I think you might want to look into getting at “lastrowid” manually, there is usually a function you can execute like “scope_identity()” that can give it to you, usually as a second SELECT. these are easy to integrate into dialects.
If you really want to disable bound parameters there’s a flag “literal_binds” that’s on Compiler, but it isn’t going to work for things like dates unless you implement renderers for them. Lycovian <mfwil...@gmail.com> wrote: > The Teradata ODBC driver is capable of returning the lastrowid inserted on an > identity column if the appropriate ODBC.INI setting is enabled. > Unfortunately, for some reason, this functionality only works if the query > doesn't have bind parameters. Sigh. > > It not what I want to do but is it possible to get SA to render all of it's > queries sent to PyODBC with the bind variables inline so the query would be > executed as a un-parameterized query by the Teradata ODBC driver? > > > > -- > 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 http://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. -- 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 http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
