[sqlalchemy] Polymorphic AbstractConcreteBase , eager load , conditions , etc

I tried to use AbstractConcreteBase for polymorphic relationships , but I am getting errors. The examples in sqlalchemy cover normal polymorphism well, but not those with Abstract Base classes. I have already asked a question on stack overflow

[sqlalchemy] Re: How to maintain a tight transactional scope whilst allowing lazy loading / attribute refreshing?

On Tuesday, 6 March 2018 22:30:46 UTC+1, Jonathan Vanasco wrote: > > > > On Tuesday, March 6, 2018 at 3:23:42 PM UTC-5, KCY wrote: >> >> I recall coming upon a section about this in the SQLAlchemy docs, >> although I can't remember where exactly. It's not the problem (if you can >> call it

[sqlalchemy] Re: How to maintain a tight transactional scope whilst allowing lazy loading / attribute refreshing?

On Tuesday, March 6, 2018 at 3:23:42 PM UTC-5, KCY wrote: > > I recall coming upon a section about this in the SQLAlchemy docs, although > I can't remember where exactly. It's not the problem (if you can call it > that) that I'm describing here. I should double check to make sure the > design

Re: [sqlalchemy] How to maintain a tight transactional scope whilst allowing lazy loading / attribute refreshing?

On Tuesday, 6 March 2018 21:12:01 UTC+1, Mike Bayer wrote: > > On Tue, Mar 6, 2018 at 2:52 PM, KCY >> wrote: >> > First off thank you for the quick reply. I have seen those resources >> you >> > linked a few days ago and it guided me partially to my current ideas. >>

[sqlalchemy] Re: How to maintain a tight transactional scope whilst allowing lazy loading / attribute refreshing?

I recall coming upon a section about this in the SQLAlchemy docs, although I can't remember where exactly. It's not the problem (if you can call it that) that I'm describing here. I should double check to make sure the design doesn't expect to have concurrent edits on the same objects. On

Re: [sqlalchemy] How to maintain a tight transactional scope whilst allowing lazy loading / attribute refreshing?

On Tue, Mar 6, 2018 at 2:52 PM, KCY wrote: > First off thank you for the quick reply. I have seen those resources you > linked a few days ago and it guided me partially to my current ideas. The > RepositoryContext class is essentially the contextmanager example with some >

Re: [sqlalchemy] Re: not announcing minor releases on the mailing list or twitter for now

On Tue, Mar 6, 2018 at 2:47 PM, Jonathan Vanasco wrote: > I can possibly help with the Twitter/blog stuff, I know that sort of stuff > well. > > I'll absolutely try to help, I'm just not sure I can do what you exactly > envision in a convenient timeframe. that's the thing,

[sqlalchemy] Re: How to maintain a tight transactional scope whilst allowing lazy loading / attribute refreshing?

(Third time's the charm, I messed up my original reply) First off thank you for the quick reply. I have seen those resources you linked a few days ago and it guided me partially to my current ideas. The RepositoryContext class is essentially the contextmanager example with some extra helper

[sqlalchemy] Re: How to maintain a tight transactional scope whilst allowing lazy loading / attribute refreshing?

I didn't mean to include that whole message history and I can't seem to edit/delete it. My apologies. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See

Re: [sqlalchemy] How to maintain a tight transactional scope whilst allowing lazy loading / attribute refreshing?

First off thank you for the quick reply. I have seen those resources you linked a few days ago and it guided me partially to my current ideas. The RepositoryContext class is essentially the contextmanager example with some extra helper methods. I think in trying to keep my example concise I

[sqlalchemy] Re: not announcing minor releases on the mailing list or twitter for now

I can possibly help with the Twitter/blog stuff, I know that sort of stuff well. I'll absolutely try to help, I'm just not sure I can do what you exactly envision in a convenient timeframe. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To

not announcing minor releases on the mailing list or twitter for now

Hi all - Some of you may have noticed that several SQLAlchemy releases have gone out in the past few weeks without my customary email on these lists, nor without a tweet from the SQLAlchemy twitter account. The reason for this is that I have created scripts that comprehensively run through the

[sqlalchemy] not announcing minor releases on the mailing list or twitter for now

Hi all - Some of you may have noticed that several SQLAlchemy releases have gone out in the past few weeks without my customary email on these lists, nor without a tweet from the SQLAlchemy twitter account. The reason for this is that I have created scripts that comprehensively run through the

Re: [sqlalchemy] How to maintain a tight transactional scope whilst allowing lazy loading / attribute refreshing?

On Tue, Mar 6, 2018 at 5:14 AM, KCY wrote: > Context > > I'm currently designing the business and persistence layer that is going to > be used in various frontend applications (Web and standalone). To that end > I've been trying to reconcile ORM entities with a tight

[sqlalchemy] How to maintain a tight transactional scope whilst allowing lazy loading / attribute refreshing?

*Context* I'm currently designing the business and persistence layer that is going to be used in various frontend applications (Web and standalone). To that end I've been trying to reconcile ORM entities with a tight session scope but I'm constantly running into the same issues. For web I