Right. There's not only the question about the session lifetime. "Where do happen the session modifications" seems a non-trivial question with large applications. I've tried a layer architecture. There's exactly one layer knowing of [and modifying] the session. But that architecture is broken in a few places where it turned out to become too verbose. (=>Individual mistakes or improper architecture?) Maybe we can do nothing but only individually design an architecture with each application. There might still be a way to find named patterns for session usage. I'd appreciate the latter ! Ruben
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
