Re: pgsql: Add PL/pgSQL SQLSTATE and SQLERRM support

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Add PL/pgSQL SQLSTATE and SQLERRM support
Date: 2005-06-02 14:20:35
Message-ID: 13517.1117722035@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-patches

Neil Conway <neilc(at)samurai(dot)com> writes:
> I should have commented on this earlier: I don't think exact Oracle
> compatibility is _at all_ important.

The results of Pavel's experiments prove that Oracle's behavior is
pretty random --- it looks to me like the chance results of whatever
quick-and-dirty implementation someone chose long ago, rather than
behavior that was thought out and agreed to. I concur that we shouldn't
feel a compulsion to match it exactly, especially seeing that we
aren't going to match it exactly in terms of the contents of the
variables, let alone fine details of what they may contain at different
times.

> As for "what makes the most sense", I like Tom's proposal here:
> http://archives.postgresql.org/pgsql-committers/2005-05/msg00311.php

> Does this sound reasonable to people?

Sounds good to me of course ;-)

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Pavel Stehule 2005-06-02 14:28:33 Re: pgsql: Add PL/pgSQL SQLSTATE and SQLERRM support
Previous Message Neil Conway 2005-06-02 14:15:09 Re: pgsql: Add PL/pgSQL SQLSTATE and SQLERRM support

Browse pgsql-patches by date

  From Date Subject
Next Message Luke Lonergan 2005-06-02 14:24:28 Re: COPY fast parse patch
Previous Message Neil Conway 2005-06-02 14:15:09 Re: pgsql: Add PL/pgSQL SQLSTATE and SQLERRM support