#1065: There should be a way to specify which controller methods are wrapped in
a
transaction
-------------------------+--------------------------------------------------
Reporter: goodwill | Owner: kskuhlman
Type: enhancement | Status: new
Priority: normal | Milestone: 1.5
Component: TurboGears | Version: 0.9a1
Severity: normal | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Comment (by dbrattli):
The patch transactions-15.diff is a draft implementation of repoze.tm
wrapped in a cherrypy tool. It replaces the transaction handling in
turbogears.expose() and also makes it possible to use transactions in
cherrypy.expose methods if needed.
TODO:
1) Remove run_with_transaction() stuff from controllers.expose() so we can
have tg exposed methods running without transactions.
2) Use zope.sqlalchemy instead of the SADataManager
3) Add a turbogears/database module dir to keep the database/transactions
files. Put the datamangers in a separate file?
4) Have a SODataManager for each PackageHub?
Comments and suggestions are welcome
-- Dag
--
Ticket URL: <http://trac.turbogears.org/ticket/1065#comment:7>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
