| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | <pgsql-hackers(at)postgreSQL(dot)org>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
| Subject: | Re: Syntax decisions for pl/pgsql RAISE extension |
| Date: | 2008-05-12 17:33:45 |
| Message-ID: | 48283942.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Now, the elephant in the room is the issue of Oracle compatibility.
> None of this looks anything even a little bit like Oracle's RAISE
> command. Oracle allows
> RAISE exception_name ;
> RAISE ;
I'm probably in the minority, but I care more about SQL/PSM
compatibility than Oracle compatibility. I would hope that the ISO
standard is at least a gorilla sitting in the corner of the room.
If it's not too impractical, a nod toward these would be good:
DECLARE condition-name CONDITION FOR SQLSTATE VALUE character-literal
SIGNAL condition-name
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-05-12 17:35:35 | Re: [COMMITTERS] pgsql: Convert wal_sync_method to guc enum. |
| Previous Message | Andrew Dunstan | 2008-05-12 17:25:26 | Re: Setting a pre-existing index as a primary key |