Re: Unrecognized exception condition "deprecated_feature"
От | Tom Lane |
---|---|
Тема | Re: Unrecognized exception condition "deprecated_feature" |
Дата | |
Msg-id | 24803.1520635455@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Unrecognized exception condition "deprecated_feature" ("David G. Johnston" <david.g.johnston@gmail.com>) |
Ответы |
Re: Unrecognized exception condition "deprecated_feature"
Re: Unrecognized exception condition "deprecated_feature" |
Список | pgsql-bugs |
"David G. Johnston" <david.g.johnston@gmail.com> writes: > On Fri, Mar 9, 2018 at 11:55 AM, Kouber Saparev <kouber@gmail.com> wrote: >> For some reason using an error code of 'deprecated_feature' does not work, >> while its equivalent '01P01' works just fine. > While I haven't looked at the source code or docs for this I'm wondering > why you believe this is a bug in the first place. This isn't specific to ERRCODE_WARNING_DEPRECATED_FEATURE; if you look at generate-plerrcodes.pl you'll see it only collects error codes, not warning codes, for use in plpgsql's mapping table. It's documented, too: Appendix A says (Note that PL/pgSQL does not recognize warning, as opposed to error, condition names; those are classes 00, 01, and 02.) I'm not entirely sure why we have this errcode at all, as it doesn't seem to be used anywhere. regards, tom lane
В списке pgsql-bugs по дате отправления: