Re: [sqlalchemy] Potential bug with .exists() queries and subqueryloads

> > however, I can't think of any reason public use of .subquery() or > .exists() would ever *want* eagerloaded options to take place since by > definition .subquery() and .exists() are never used to load objects. > So in 1.2 I'll propose to make this automatic > Yep, I agree with this!

Re: [sqlalchemy] Potential bug with .exists() queries and subqueryloads

On Tue, Jul 18, 2017 at 2:13 PM, wrote: > Hello, I'm running into some difference in behavior for .exists() in > SQLAlchemy 1.0.17 and 1.1.11, related to subqueryloads. > > > class A(db.Model): > __tablename__ = 'a' > > id = db.Column(db.Integer, primary_key=True) >