| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Urbański <wulczer(at)wulczer(dot)org> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp> |
| Subject: | Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.) |
| Date: | 2010-12-26 20:17:15 |
| Message-ID: | 19946.1293394635@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
=?UTF-8?B?SmFuIFVyYmHFhHNraQ==?= <wulczer(at)wulczer(dot)org> writes:
> Makes sense. Wait, no, errcodes.sgml includes the entries for success
> and warnings, but the plpgsql conditions list does not. So we need a
> separate column to differentiate.
OK. But not 0/1 please. Maybe 'E', 'W', or 'S' ? And again, fixed
width columns first, so something like
sqlstate E/W/S errcode_macro_name plpgsql_condition_name
where I guess we could still make the plpgsql condition name optional.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-12-26 20:27:11 | Re: Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED. |
| Previous Message | Robert Haas | 2010-12-26 20:14:52 | Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-12-26 20:27:11 | Re: Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED. |
| Previous Message | Robert Haas | 2010-12-26 20:14:52 | Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.) |