Ah ha!
I figured this out. It was a mix of a lazy eye and some peculiarities
between Postgres(live) and sqlite(test-case).
Given the query:
session.query(Foo).options(contains_eager('bar')).order_by(Foo.id.desc()).offset(0).limit(100).all()]
The SQL is (approx)
select foo.*, bar.* from foo, bar order by foo.id desc limit 100;
I didn't notice that there wasn't a `join` from foo to bar until I
reformatted the SQL.
SqlAlchemy just drops in the 'bar' on the query.
In such a case, shouldn't the library ideally:
• raise some error
or
• not add in the "join"
?
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
