Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.)
От | Jan Urbański |
---|---|
Тема | Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.) |
Дата | |
Msg-id | 4D17A10E.4040005@wulczer.org обсуждение исходный текст |
Ответ на | Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.)
Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.) |
Список | pgsql-hackers |
On 26/12/10 20:57, Tom Lane wrote: > Jan Urbański <wulczer@wulczer.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? 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. > Things might line up nicer if the sqlstate is the first column. I was thinking of separating the values with tabs anyway, but I'm fine with putting sqlstate first. Cheers, Jan
В списке pgsql-hackers по дате отправления: