Re: [sqlalchemy] Updating polymorphic parent from polymorphic child's event

Worked perfectly. Thanks for the help. On Thursday, August 3, 2017 at 11:16:26 AM UTC-7, Mike Bayer wrote: > > On Thu, Aug 3, 2017 at 1:37 PM, Colton Allen > wrote: > > I've got an event that's trying to update another model with a foreign > key > > but it's raising a

Re: [sqlalchemy] Updating polymorphic parent from polymorphic child's event

On Thu, Aug 3, 2017 at 1:37 PM, Colton Allen wrote: > I've got an event that's trying to update another model with a foreign key > but it's raising a strange error that I'm having trouble debugging. > "AttributeError: 'Join' object has no attribute 'implicit_returning'". >

[sqlalchemy] Updating polymorphic parent from polymorphic child's event

I've got an event that's trying to update another model with a foreign key but it's raising a strange error that I'm having trouble debugging. "AttributeError: 'Join' object has no attribute 'implicit_returning'". The query worked in the past (before the OutboundModel became polymorphic).

SQLAlchemy 1.1.13 released

SQLAlchemy release 1.1.13 is now available. This release modifies the just-released fix for Oracle "WITH_UNICODE" mode based on feedback from cx_Oracle developers, to resolve a performance regression caused by this change. Changelog for 1.1.13 is at:

[sqlalchemy] SQLAlchemy 1.1.13 released

SQLAlchemy release 1.1.13 is now available. This release modifies the just-released fix for Oracle "WITH_UNICODE" mode based on feedback from cx_Oracle developers, to resolve a performance regression caused by this change. Changelog for 1.1.13 is at:

SQLAlchemy 1.0.19 released

SQLAlchemy release 1.0.19 is now available. This release modifies the just-released fix for Oracle "WITH_UNICODE" mode based on feedback from cx_Oracle developers, to resolve a performance regression caused by this change. Changelog for 1.0.19 is at:

[sqlalchemy] SQLAlchemy 1.0.19 released

SQLAlchemy release 1.0.19 is now available. This release modifies the just-released fix for Oracle "WITH_UNICODE" mode based on feedback from cx_Oracle developers, to resolve a performance regression caused by this change. Changelog for 1.0.19 is at: