Re: "database.py -> uses a CP filter to handle transactions which could be implemented as middleware or in the base controller itself. Using SQLAlchemy by default but supportin SQLObject too (maybe they can be splitted into two different components altogether which share the same interface?)"
I would like to see this happen; an ORM is a dumb place to manage connections, since there's little high-level about connections. I outlined some ideas here recently: http://mail.python.org/pipermail/db-sig/2006-November/004855.html
Also sqlapi (itself dormant) is an attempt to extract some of this: http://sqlobject.org/sqlapi/
Additionally some kind of transaction container is required; Zope's seems fine and simple, except that it needs to be properly extracted from Zope. I expect that higher-level database tools will probably add themselves to the transactional container (in addition to the database connections they manage), so that they can effectively monitor the state of the transaction that way.
-- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
