| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Marko Tiikkaja <pgmail(at)joh(dot)to>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: enable new error fields in plpgsql (9.4) |
| Date: | 2013-06-28 16:08:21 |
| Message-ID: | 20130628160821.GC924898@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 28, 2013 at 05:21:29PM +0200, Pavel Stehule wrote:
> 2013/6/28 Noah Misch <noah(at)leadboat(dot)com>:
> > Okay. I failed to note the first time through that while the patch uses the
> > same option names for RAISE and GET STACKED DIAGNOSTICS, the existing option
> > lists for those commands differ:
> >
> > --RAISE option-- --GET STACKED DIAGNOSTICS option--
> > ERRCODE RETURNED_SQLSTATE
> > MESSAGE MESSAGE_TEXT
> > DETAIL PG_EXCEPTION_DETAIL
> > HINT PG_EXCEPTION_HINT
> > CONTEXT PG_EXCEPTION_CONTEXT
> >
> > To be consistent with that pattern, I think we would use COLUMN, CONSTRAINT,
> > TABLE, TYPE and SCHEMA as the new RAISE options.
>
> I understand to your motivation, but I am not sure. Minimally word
> "TYPE" is too general. I have not strong opinion in this area. maybe
> DATATYPE ??
I'm not positive either. DATATYPE rather than TYPE makes sense.
> p.s. you cannot to specify CONTEXT in RAISE statement
Oops; right.
--
Noah Misch
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2013-06-28 16:09:59 | Re: ALTER TABLE ... ALTER CONSTRAINT |
| Previous Message | Stefan Kaltenbrunner | 2013-06-28 15:58:55 | Re: PostgreSQL 9.3 latest dev snapshot |