Re: [HACKERS] ToDo: enhanced diagnostic for plpgsql
Excerpts from Pavel Stehule's message of sáb nov 27 04:46:08 -0300 2010: Hello do you plan do some work on this job? Not currently :-( -- Álvaro Herrera alvhe...@commandprompt.com The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] ToDo: enhanced diagnostic for plpgsql
Hello there is difficult working with exception still. Isn't time to move forward? http://archives.postgresql.org/pgsql-general/2010-11/msg01129.php I am thinking, so we can little bit enhance a GET DIAGNOSTICS statement condition item names are defined in SQL 92 - mainly: TABLE_NAME, COLUM_NAME and MESSAGE_TEXT. Regards Pavel Stehule -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] ToDo: enhanced diagnostic for plpgsql
Excerpts from Pavel Stehule's message of vie nov 26 07:37:42 -0300 2010: Hello there is difficult working with exception still. Isn't time to move forward? http://archives.postgresql.org/pgsql-general/2010-11/msg01129.php I am thinking, so we can little bit enhance a GET DIAGNOSTICS statement condition item names are defined in SQL 92 - mainly: TABLE_NAME, COLUM_NAME and MESSAGE_TEXT. This is probably connected to my proposal here: http://archives.postgresql.org/message-id/20090804171210.gl6...@alvh.no-ip.org -- Álvaro Herrera alvhe...@commandprompt.com The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] ToDo: enhanced diagnostic for plpgsql
2010/11/26 Alvaro Herrera alvhe...@commandprompt.com: Excerpts from Pavel Stehule's message of vie nov 26 07:37:42 -0300 2010: Hello there is difficult working with exception still. Isn't time to move forward? http://archives.postgresql.org/pgsql-general/2010-11/msg01129.php I am thinking, so we can little bit enhance a GET DIAGNOSTICS statement condition item names are defined in SQL 92 - mainly: TABLE_NAME, COLUM_NAME and MESSAGE_TEXT. This is probably connected to my proposal here: http://archives.postgresql.org/message-id/20090804171210.gl6...@alvh.no-ip.org yes, your proposal means first step Pavel -- Álvaro Herrera alvhe...@commandprompt.com The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] ToDo: enhanced diagnostic for plpgsql
Hello do you plan do some work on this job? Regards Pavel Stehule 2010/11/26 Alvaro Herrera alvhe...@commandprompt.com: Excerpts from Pavel Stehule's message of vie nov 26 07:37:42 -0300 2010: Hello there is difficult working with exception still. Isn't time to move forward? http://archives.postgresql.org/pgsql-general/2010-11/msg01129.php I am thinking, so we can little bit enhance a GET DIAGNOSTICS statement condition item names are defined in SQL 92 - mainly: TABLE_NAME, COLUM_NAME and MESSAGE_TEXT. This is probably connected to my proposal here: http://archives.postgresql.org/message-id/20090804171210.gl6...@alvh.no-ip.org -- Álvaro Herrera alvhe...@commandprompt.com The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
