"Mike Bayer" <mike_not_on_goo...@zzzcomputing.com> writes: > it looks like you're trying to add an ORDER BY to the table that's > only there via joinedload(). That's *really* not something we > anticipate and it would be better if people proposed perhaps ad-hoc > order_by expressions to be added to common loader options like > joinedload() and selectinload(), in the same way that we offer ad-hoc > WHERE criteria for these options now. as you are probably aware, the > current way to do "joinedload with custom criteria / ordering / etc" > is to write the query using outerjoin() and order_by() normally, then > use contains_eager().
Oh, thanks a lot for this!. Accordingly with the git history, I introduced that test to address a deprecation warning issued by SA 1.4+ load_only()... I will study the contains_eager() alternative and try to modernize my code that still uses that idiom. bye, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. l...@metapensiero.it | -- Fortunato Depero, 1929. -- 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 http://stackoverflow.com/help/mcve for a full description. --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/87zg576sun.fsf%40metapensiero.it.
