| 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 19:57:26 |
| Message-ID: | 19558.1293393446@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:
> How about a format like this then:
> # Comment
> Section: Class 2F - SQL Routine Exception
> macro_name sqlstate plpgsqlname is_error
> That is: # and blank lines are comments, lines starting with "Section:"
> are section names (needed for SGML output), the rest are whitespace
> separated strings. is_error is 0 or 1, if it's 0 we don't generate a
> plpgsql condition for it.
Or just leave out the plpgsqlname if we don't want a condition to be
generated?
Things might line up nicer if the sqlstate is the first column.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Urbański | 2010-12-26 20:09:50 | Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.) |
| Previous Message | Jan Urbański | 2010-12-26 19:45:10 | Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Urbański | 2010-12-26 20:09:50 | Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.) |
| Previous Message | Jan Urbański | 2010-12-26 19:45:10 | Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.) |