Hello. I've read the patch and the new documentation and i've learned about the existence of select_entity_from(). I was trying to say that the new documentation does not help me to understand the meaning / preferred usage of these constructs (i.e. select_from, select_entity_from and aliased). I simply don't understand when should I use which and why.
I have already solved my original problem by replacing select_from() with add_entity() and join(). Take a look at older posts in this thread for more details if you're interested, though the original query is a bit more involved than the supplied regression. Ladislav Lenart On 31.5.2013 12:06, Andrija Zarić wrote: > On Friday, May 31, 2013 11:46:46 AM UTC+2, Ladislav Lenart wrote: > > Glad I could help, but I don't understand what is going on. Neither ticket > description nor the patch itself helped me. Sorry. > > What is select_from() good for when it generates a cartesian query? > > What MIGHT help ME (a lot infact) is a couple of DOs and DONTs examples > in one > place for all these three constructs > > OR > > A 'highlevel user-friendly step-by-step description' about what each > construct > does, so that I can see where they differ. > > > Hi, Lenart! > > In the patch you can find doc for the new method Query.select_entity_from. As > I > read it, it replaces Query.select_from. > > Have you tried simply replacing old method with the new one (after applying > the > patch)? > > a. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
