#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 | Keywords:
------------------------+---------------------------------------------------
'''Summary'''
If we use multiple flushes (SQLAlchemy) sequentially in a controller
method, and some exception occurs in between, all the flushed data should
ideally rollback. It's because the controller method is automatically
encapsulated in a transaction by TurboGears.
But it is not happening in the sample project attached.
'''Description about the attached sample project:'''
''Models:'' Website, Page
''Business rules:''
1. An website can consist of multiple pages.
2. An website has a home page.
3. Whenever a website is created, a homepage is created as well.
''Url for creating an website (problem is shown here):''
http://localhost:8080/tran
--
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
-~----------~----~----~----~------~----~------~--~---
