eval() was definitely not doing what I expected. Thanks for the tip about getattr(), and thanks for helping get my head screwed on right!
Greg-- On Wednesday, March 25, 2015 at 11:33:44 AM UTC-5, Jonathan Vanasco wrote: > > Yeah, there's no reason to touch eval -- and a lot of reasons not to. > Security issues aside, when you make a mistake the error will be > completely unintelligible. > > You can create joins dynamically very easily by just iteratively building > up on it, and using getattr() if needed. > > If you're doing any advanced things (subqueries, aliases, etc), I would > suggest keeping the online docs loaded in a browser window and paying close > attention to the return values. Most operations will return a query, but a > few will return another object. > -- 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.
