> I like this approach. One of the nice things about Oracle is that
> they have an error manual. All Oracle errors have an associated
> number. You can look up that number in the error manual to find a
> paragraph giving details and workarounds. Admittedly, sometimes the
> further details are not helpful, but sometimes they are. The basic
> idea of being able to look up an error lets programmers balance the
> need for a terse error message with the need for a fuller explanation.
One of the examples when you need exact error message code is when you want
to separate unique index violations from other errors. This often needed when
you want just do insert, and leave all constraint checking to database...
--
Sincerely Yours,
Denis Perchine
----------------------------------
E-Mail: [EMAIL PROTECTED]
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
