Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.databases.postgresql > #307

Re: User-defined type -- error handling

From Don Y <this@isnotme.com>
Newsgroups comp.databases.postgresql
Subject Re: User-defined type -- error handling
Date 2012-02-14 20:53 -0700
Organization Aioe.org NNTP Server
Message-ID <jhfa88$14k$1@speranza.aioe.org> (permalink)
References <jh90df$435$1@speranza.aioe.org> <jhakkj$2bn$1@reversiblemaps.ath.cx>

Show all headers | View raw


Hi Jasen,

On 2/13/2012 2:20 AM, Jasen Betts wrote:
> On 2012-02-12, Don Y<this@isnotme.com>  wrote:

>> So, I'm trying to figure out what error to throw and how
>> PG will react in that event (i.e., just abort the transaction?)
>
> 22000 looks like good starting place unless one of the other 22xxx
> errors fits better
>
> http://www.postgresql.org/docs/9.1/static/errcodes-appendix.html
>
> yes, it will abort transaction much like "select 1/0;" does.

I'm thinking of how I would be able to figure out *where*
this was biting me and how I could *fix* it, once bitten.

E.g., imagine having an assertion fail in the "out()" function.
You couldn't *see* the values that were giving those problems
(even if you could identify the rows that were involved).

I've got to stew on this a bit longer...

Back to comp.databases.postgresql | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

User-defined type -- error handling Don Y <this@isnotme.com> - 2012-02-12 11:29 -0700
  Re: User-defined type -- error handling Jasen Betts <jasen@xnet.co.nz> - 2012-02-13 09:20 +0000
    Re: User-defined type -- error handling Don Y <this@isnotme.com> - 2012-02-14 20:53 -0700

csiph-web