I'd like to avoid that, if at all possible. that was actually a solution to an earlier thing i had a few weeks ago!
I'm fine with doing suqueryloads instead of joinedloads or hitting the database multiple times. with my current design... building another query where i need to specify loads will be too much of an undertaking. the only shortcut i could take would be constructing the query by pulling the session out of the object, then piping in the object's id as the filter... and that would just be too messy. -- 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.
