we needed it for....oh MS-SQL tables that have triggers. On May 4, 2010, at 3:11 PM, Kent Bower wrote:
> You think of everything? ;) Thanks > > On 5/4/2010 2:41 PM, Michael Bayer wrote: >> On May 4, 2010, at 2:30 PM, Kent wrote: >> >> >>> I understand I can disable RETURNING for an engine with >>> 'implicit_returning=False' >>> >>> Is there a way to do this for certain primary key columns only, but >>> not disabled engine-wide? >>> >>> (We've done some flexible view creation so that our app (sqlalchemy) >>> sees the same database metadata whether we are on a legacy oracle >>> system or a postgres database. In some cases the 'tables' are views >>> that don't support RETURNING, so I'd like to turn it off for those >>> cases only...) >>> >> Table() accepts it as a keyword argument as well. >> >> >> > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to sqlalch...@googlegroups.com. > To unsubscribe from this group, send email to > sqlalchemy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
