Hi all, I've just released Lead (pun intended), aka collective.lead, a minimalist Zope 2/SQLAlchemy integration package.
http://cheeseshop.python.org/pypi/collective.lead There are at least two other Zope2/SA integration packages that I know of - z3c.sqlalchemy and ore.alchemist. Both of these are more ambitious in supporting particular Zope functionality (e.g. restricted python, encapsulation of a "model" of mapper relationship and a convenience API around mappers in the case of z3c.sqlalchemy; bridges to zope.interface and zope.formlib for form auto-generation in the case of ore.alchemist). However, I needed something very simple which only concerned itself with managing connections and transactions, and provided hooks to make it easy to configure the engine (and in particular the DSN) at runtime rather than at module-level. In particular, I didn't want to build any abstractions on top of SA's APIs. If anyone finds this useful, great. :) Many thanks to Andreas Jung and Kapil Thangavelou, the authors of the two other packages above, whose brains I picked and code I stole, and to Jason Kirtland and others in #sqlalchemy, for helping me understand threadlocals and connection management (I hope). Martin --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
