| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Leon Starr <leon_starr(at)modelint(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: How to trap invalid enum input exception? |
| Date: | 2010-08-16 03:58:46 |
| Message-ID: | 12693.1281931126@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Leon Starr <leon_starr(at)modelint(dot)com> writes:
> I have tried catching following with no success:
> INVALID_TEXT_REPRESENTATION
> SQLSTATE '22P02'
> SQLSTATE '22000'
> DATA_EXCEPTION
> OTHERS
> (lest we think I am completely incompetent ;), I have had success
> catching all manner of FOREIGN_KEY_VIOLATION, UNIQUE_VIOLATION, CHECK_VIOLATION, NO_DATA_FOUND, etc. in other functions. So something is very different about this particular exception!)
> It seems to me that it is not a normal exception and evades the exception clause. Any thoughts on where to go from here?
Hmm, maybe the error is not being thrown when/where you think it is?
Coercions of constants, in particular, happen very early and might
possibly need some contortions to catch. Could we see an exact example
of what's not working for you?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Kupershmidt | 2010-08-16 15:50:55 | Re: Listing Schemas - Revisited |
| Previous Message | Leon Starr | 2010-08-16 03:53:50 | Re: How to trap invalid enum input exception? |