Re: [sqlalchemy] sqlalchemy.orm.exc.StaleDataError upon migration from SQLAlchemy 1.1.15 to 1.2.0 or 1.2.1

On 02/12/2018 01:32 PM, Mike Bayer wrote: > I've loaded up mailman's test suite and one step at a time reduced the > failing test to more granular steps, removing one at a time to > continue to reproduce the error. It turns out there is a fundamental > bug in the post_update feature that has

Re: [sqlalchemy] sqlalchemy.orm.exc.StaleDataError upon migration from SQLAlchemy 1.1.15 to 1.2.0 or 1.2.1

I've loaded up mailman's test suite and one step at a time reduced the failing test to more granular steps, removing one at a time to continue to reproduce the error. It turns out there is a fundamental bug in the post_update feature that has existed for years and is only becoming apparent now

Re: [sqlalchemy] sqlalchemy.orm.exc.StaleDataError upon migration from SQLAlchemy 1.1.15 to 1.2.0 or 1.2.1

On Sat, Jan 27, 2018 at 11:54 PM, wrote: > Hi Mike, > > I am one of the other Mailman developers, just following up on behalf of > Mark. > > On Sunday, 21 January 2018 06:51:29 UTC-8, Mike Bayer wrote: >> >> here are a few questions: >> >> 1. is mailman using the

Re: [sqlalchemy] sqlalchemy.orm.exc.StaleDataError upon migration from SQLAlchemy 1.1.15 to 1.2.0 or 1.2.1

Hi Mike, I am one of the other Mailman developers, just following up on behalf of Mark. On Sunday, 21 January 2018 06:51:29 UTC-8, Mike Bayer wrote: > > here are a few questions: > > 1. is mailman using the version_id mapper feature with these mappings ? > No, Mailman isn't using version_id

Re: [sqlalchemy] sqlalchemy.orm.exc.StaleDataError upon migration from SQLAlchemy 1.1.15 to 1.2.0 or 1.2.1

On Sunday, January 21, 2018 at 6:51:29 AM UTC-8, Mike Bayer wrote: > > here are a few questions: > > 1. is mailman using the version_id mapper feature with these mappings ? > > 2. do mailman mappings use natural primary keys? in the above example > are the primary keys of objects changing

Re: [sqlalchemy] sqlalchemy.orm.exc.StaleDataError upon migration from SQLAlchemy 1.1.15 to 1.2.0 or 1.2.1

here are a few questions: 1. is mailman using the version_id mapper feature with these mappings ? 2. do mailman mappings use natural primary keys? in the above example are the primary keys of objects changing? On Sun, Jan 21, 2018 at 8:24 AM, Mike Bayer wrote: > On

Re: [sqlalchemy] sqlalchemy.orm.exc.StaleDataError upon migration from SQLAlchemy 1.1.15 to 1.2.0 or 1.2.1

On Sat, Jan 20, 2018 at 8:19 PM, Mark Sapiro wrote: > Gnu Mailman 3 uses SQL Alchemy to access SQL databases. We have an issue > with one of or unit tests which passes with SQLAlchemy <= 1.1.15 but which > fails with SQLAlchemy >= 1.2. The failure is independent of the backend

[sqlalchemy] sqlalchemy.orm.exc.StaleDataError upon migration from SQLAlchemy 1.1.15 to 1.2.0 or 1.2.1

Gnu Mailman 3 uses SQL Alchemy to access SQL databases. We have an issue with one of or unit tests which passes with SQLAlchemy <= 1.1.15 but which fails with SQLAlchemy >= 1.2. The failure is independent of the backend (sglite, mysql or pgsql). Here's a traceback from the failure. Traceback