Re: [COMMITTERS] pgsql: Add STRICT to PL/pgSQL SELECT INTO, so exceptions are thrown if

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [COMMITTERS] pgsql: Add STRICT to PL/pgSQL SELECT INTO, so exceptions are thrown if
Date: 2006-06-16 21:55:54
Message-ID: 1050.1150494954@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> Plan B is to invent new errcodes to match the Oracle spellings. If
>> that's what we want to do, it's not that hard.

> We could use:
> #define ERRCODE_DATA_EXCEPTION MAKE_SQLSTATE('2','2',
> or
> #define ERRCODE_ERROR_IN_ASSIGNMENT MAKE_SQLSTATE('2','2',

Those are both mighty generic (in fact DATA_EXCEPTION is a class code
not a specific error). If we want to stick to existing errcodes I think
CARDINALITY_VIOLATION is the only reasonable choice.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2006-06-16 22:01:18 pgsql: Document issues with non-default tablespaces and pg_dumpall
Previous Message Bruce Momjian 2006-06-16 21:41:24 pgsql: Add URL for ISO dates: >

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-06-16 22:02:45 Re: [COMMITTERS] pgsql: Add STRICT to PL/pgSQL SELECT INTO, so exceptions
Previous Message Bruce Momjian 2006-06-16 21:36:58 Re: pg_dump -Ft failed on Windows XP