[EMAIL PROTECTED] schrieb:
> Well after an hour or so of mucking around, I finally found out how to
> catch an IntegrityError.
> 
> http://docs.turbogears.org/1.0/SqlObjectGotchas
> 
> No wonder I couldn't catch it.
> 
> Has anyone figured out something more elegant?

Well, of course you can just assign
'hub.hub.getConnection().module.IntegrityError' to shorter name at the
top of our file.

Alternatively, write wrapper functions/methods for you data model access
 code and through better (custom) exceptions in them.

> Is this in fact, for sure, a bug in SQLObject and not TG?  If so, I'll
> take it the SQLObject mailing list, and hopefully get it fixed.

Definitely SQLObject.

Chris

--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to