Re: [sqlalchemy] Re: executemany() incorrectly used for updates to a table with row versioning with psycopg2

Hi Mike, Your fix worked - the example I gave and our other tests pass now. Many thanks, Tom On Mon, 19 Oct 2015 at 17:19 Mike Bayer wrote: > > > On 10/19/15 11:57 AM, Mike Bayer wrote: > > > > > > On 10/19/15 11:44 AM, Steven Winfield wrote: > >> The problem seems

Re: [sqlalchemy] Re: executemany() incorrectly used for updates to a table with row versioning with psycopg2

On 10/19/15 11:44 AM, Steven Winfield wrote: > The problem seems to be that the result set from an executemany() call > in psycopg2 is discarded - here is a good stackoverflow article on this > subject: >

[sqlalchemy] Re: executemany() incorrectly used for updates to a table with row versioning with psycopg2

The problem seems to be that the result set from an executemany() call in psycopg2 is discarded - here is a good stackoverflow article on this subject: http://stackoverflow.com/questions/21624844/getting-ids-of-multiple-rows-inserted-in-psycopg2 In _emit_update_statements in orm/persistence.py,

Re: [sqlalchemy] Re: executemany() incorrectly used for updates to a table with row versioning with psycopg2

On 10/19/15 11:57 AM, Mike Bayer wrote: > > > On 10/19/15 11:44 AM, Steven Winfield wrote: >> The problem seems to be that the result set from an executemany() call >> in psycopg2 is discarded - here is a good stackoverflow article on this >> subject: >>