| From: | PFC <lists(at)boutiquenumerique(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Markus Bertheau" <twanger(at)bluetwanger(dot)de> |
| Cc: | 'PostgreSQL' <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: getting details about integrity constraint violation |
| Date: | 2005-06-03 18:42:34 |
| Message-ID: | op.srs4w8kzth1vuj@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> The "error fields" facility in the FE/BE protocol could be extended
> in that direction, and I think there's already been some discussion
> about it; but no one has stepped up with a concrete proposal, much
> less volunteered to do the work ...
Um, if changing the protocol is a bother, you could also add parseable
infos to the error messages...
instead of :
"ERROR: duplicate key violates unique constraint "testinteg_one_key""
it would say
"ERROR: duplicate key violates unique constraint "testinteg_one_key"
[code:"XXXX" error:"integrity" type:"unique" column:"something"
constraint:"testinteg_one_key"]"
Which could be hackfully added by a "parseable" locale (but with a more
restrained form...)
SET lc_messages TO parseable
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajesh Kumar Mallah | 2005-06-04 11:26:56 | Tsearch2 headline usage |
| Previous Message | Bruno Wolff III | 2005-06-03 15:36:59 | Re: 'true'::TEXT::BOOLEAN |