that's fine. this is for a webapp where we have in a single request :
begin; user = .filter().first() DO LOTS OF STUFF, all over the place DO EVEN MORE STUFF , in more places user = .get(user_id) commit; if this behavior is intended, then we can just rely on it for now. otherwise we need to refactor a lot of code to explicitly pass around the User object. until today, we only needed to operate on user_ids , now we need to check a value on the user object in 5 places (only on a particular url). i don't want to hit the db 5x. -- 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/groups/opt_out.
