On Wednesday 31 May 2006 21:28, Oleg Broytmann wrote: > There is an item in the TODO to unify exceptions. But nobody's > working on it now. Do you want to be the one?
What is the intention regarding this? Is the plan to raise a single generic exception (say DatabaseError) with specific details about the error, or the desire is to have a hierarchy of exceptions like the backends have (DatabaseError, IntegrityError, OperationalError, ...)? Because a single generic exception will be pretty easy to add (just a guess without looking at the code), while having a hierarchy will be more complex as mappings between backend errors and sqlobject errors need to be made and a common denominator needs to be found between backend exceptions. However even if the desire is to have a hierarchy of exceptions, it can probably start with a generic exception which should be easy to add and then expand by gradually adding the others over time as need arises (i.e. all database errors in a backend map to the generic exception unless some of them are specifically mapped to a more specific exception from the sqlobject hierarchy) -- Dan ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
