On Wednesday, April 4, 2018 at 4:49:16 PM UTC-4, Mike Bayer wrote: > > I've not seen any context for what you're doing so is using > "query.select_from()" part of how you want to handle this? >
My personal fix was just to flip the order of entities submitted to `.query()` - but I could have used `.select_from()`. It was already handled when I first posted - I was just wondering "why". Now I know - the order of entities is deterministic to the generated sql. The behavior wasn't documented in the API under 'query' or 'join', but was in the tutorial. I was refactoring an expensive query yesterday, and a few columns got deleted or moved around from the query's components. I never experienced this in... 10+ years of SqlAlchemy. -- 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 post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
