| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | david(dot)sahagian(at)emc(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: parsing SQLERRM ? |
| Date: | 2012-06-15 16:50:08 |
| Message-ID: | 29294.1339779008@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> writes:
> david(dot)sahagian(at)emc(dot)com wrote:
>> In my PL/pgSQL stored functions,
>> I want to be able to distinguish which FK-constraint caused the
>> [foreign_key_violation] exception.
>> Is a "robust enough" parsing of SQLERRM actually the best/only way to
>> determine this ?
> I think so.
Yeah, at the moment. There are plans to fix this, but it won't happen
before 9.3 at the earliest.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-06-15 17:20:38 | Re: Get RULE condition and commands |
| Previous Message | John Lumby | 2012-06-15 16:39:51 | INSERT INTO...RETURNING with partitioned table using trigger/rule |