Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables
От | Bruce Momjian |
---|---|
Тема | Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables |
Дата | |
Msg-id | 200504190359.j3J3xDP02838@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables for (Pavel Stehule <stehule@kix.fsv.cvut.cz>) |
Ответы |
Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables
Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables for Re: [HACKERS] Implementation of SQLCODE and SQLERRM |
Список | pgsql-patches |
Guys, is this patch ready for application? I think so, but am not 100% sure. --------------------------------------------------------------------------- Pavel Stehule wrote: > Hello, > > I changed code by your and Neil's notes. The name SQLCODE isn't well, > better is SQLSTATE. It's very similar DB2 variable. I am not sure, so my > solutions is best. Propably not. It's only particular solution for > plpgsql. The files plpgsql.sql and plpgsql.out are diffs for regression > tests. > > This patch is implementation of variables SQLERRM and SQLSTATE for plpgsql > language. Variable SQLSTATE contains five chars PostgreSQL Error Code, > SQLERRM contains relevant message last catched exception. All variables > are attached to plpgsql_block and have local scope. Default values are > '00000' for SQLSTATE and 'Sucessful completion' for SQLERRM. > > Regards > > Pavel Stehule > Content-Description: [ Attachment, skipping... ] Content-Description: [ Attachment, skipping... ] Content-Description: [ Attachment, skipping... ] > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
В списке pgsql-patches по дате отправления: