#1209: Data already flushed does not rollback if exception occurs
------------------------+---------------------------------------------------
Reporter: sanjay | Owner: anonymous
Type: defect | Status: new
Priority: normal | Milestone: 1.0b3
Component: TurboGears | Version: 1.0b2
Severity: normal | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Comment (by sanjay):
> Sounds to me like what you really need is a way to INSERT that's
separate from the flush method
>(rather than changing how flush operates). This is how Dejavu works: the
Sandbox.memorize method
>does an INSERT, and can be called repeatedly within a transaction. The
Sandbox.flush_all method
>then executes COMMIT. (A Dejavu Sandbox is similar to an SQLAlchemy
Session/Unit of Work.)
Sqlalchemy's flush method does NOT commit inside a transaction. It only
inserts. I have tested it. I don't know why inside a turbogears automatic
transaction this fails.
--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/1209>
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.
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-tickets?hl=en
-~----------~----~----~----~------~----~------~--~---
