On Dec 28, 2011, at 3:28 PM, Mike Orr wrote: > >> I would think if the plugin is designed for Pyramid, it would be based >> around ZopeSQLAlchemy, which provides a master transaction for everyone to >> integrate towards. Do the third party plugins at least integrate with that ? > > Question: if multiple scoped sessions are created, each using > ZopeTransactionExtension, would they all automatically fit into the > global commit/rollback? > > Can we use the same ZopeTransactionExtension *instance* for all the > scoped sessions, or would they each need a separate instance?
yeah I'd like to get guidance from Chris McD or Lawrence Rowe on what a multiple-session integration path might be (or if all apps should really use one Session with zope.sqlalchemy). also my apologies for screwing up it's name. > >> Also, just as a note, I've never seen a 3rd party plugin that uses >> SQLAlchemy before, which is using a Session, defining tables, etc. Can I >> see one ? Are there a lot , or like half a dozen ? > > I can't remember everywhere I've seen things. There are few libraries > using SQLAlchemy yet. I mainly wanted to avoid a future mess if > everyone did things in different ways, and then had trouble > interoperating. The API you've suggested sounds the most flexible; it > won't get into anyone's way but it's there if you want it, and it can > scale to multiple datbases, Bases, and Sessions. I only ask because you know it's really hard to design a system that we're going to recommend for everyone, without a good set of concrete examples of what they need. You know we've been around this block a bunch. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
