I've had a search around, and AFAICT there's nothing else here that
throws the exception "TypeError: 'long' object is not callable" when a
rollback is performed. There are a few that throw something like
"Connection has already gone through rollback" or similar, but they
appear to be unrelated issues (reusing an already rolled-back
connection).
I think your error revolves around the try/except block, although went I read it I didn't got to the TypeError.
If you could point me towards the topic you saw it would be brilliant,
as any kind of solution to this would be very welcome.
Thanks,
Patrick
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" 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
-~----------~----~----~----~------~----~------~--~---
- [TurboGears] Re: SQLObject rollback exceptions Jorge Vargas
- [TurboGears] Re: SQLObject rollback exceptions Patrick Coleman
- [TurboGears] Re: SQLObject rollback exceptions Jorge Vargas
- [TurboGears] Re: SQLObject rollback exception... Patrick Coleman
- [TurboGears] Re: SQLObject rollback excep... Sean Jamieson
- [TurboGears] Re: SQLObject rollback excep... Jorge Vargas

