Re: [SQLObject] Catching IntegrityError and friends

[<pk...@gm...>]

On 8/20/05, Oleg Broytmann <ph...@ma...> wrote:
> On Sat, Aug 20, 2005 at 02:43:12PM +0200, Paul K?lle wrote:
> > I noticed a few exceptions coming straight from the db, namely
> > IntegrityError
>=20
>    DB API drivers can raise also OperationalError, ProgrammingError and
> other errors. To what exception should SQLObject convert them?
Start with a subset all supported DBs share.

> Is it ok to loose the distinction between one error and another?
No. Hmm, depends. If two databases handle the same error on the DB
level but give it a different name it might be appropriate to unify
them.

>=20
> > It somewhat ruins
> > database abstraction IMHO.
>=20
>    SQLObject does not guarantee full DBMS independence. I am not sure if =
it
> should try.
I'll see what I will get.

>=20
> > Is there a
> > preferred way/place to add this code?
>=20
>    dbconnection.py. Especially DBAPI._executeRetry().
>=20
> Oleg.
> --
>      Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
>            Programmers don't die, they just GOSUB without RETURN.
>