Re: Open 7.1 items

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Open 7.1 items
Date: 2001-02-14 20:28:07
Message-ID: Pine.LNX.4.30.0102142124530.1112-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian writes:

> > Bruce Momjian writes:
> >
> > > New PL/pgSQL GET DIAGNOSTICS statement for SPI value access (Jan)
> >
> > If someone can show me an example of how it operates I can write up
> > something.
>
> I found:
>
> > Quoting a recent message by Jan Wieck <janwieck(at)Yahoo(dot)com>:
> > :Do a
> > :
> > : GET DIAGNOSTICS SELECT PROCESSED INTO <int4_variable>;
> > :
> > :directly after an INSERT, UPDATE or DELETE statement and you'll know
> > :how many rows have been hit.
> > :
> > :Also you can get the OID of an inserted row with
> > :
> > : GET DIAGNOSTICS SELECT RESULT INTO <int4_variable>;
> >
>
> Looking at plpgsql/src/gram.y, it only supports PROCESSED (rows
> returned/affected) and RESULT (OID). The grammar indicates that only
> SELECT is allowed in GET DIAGNOSTICS SELECT. Jan says it works for
> INSERT/UPDATE/DELETE too, but I guess you still use GET DIAGNOSTICS
> SELECT.

May I suggest that this is the wrong syntax? It should be

GET DIAGNOSTICS <variable> = ROW_COUNT;

See SQL99 part 2, clause 19.1.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-02-14 21:16:19 Re: Open 7.1 items
Previous Message Fabio Berbert de Paula 2001-02-14 19:18:58 <1/2 OFF> PostgreSQL in cluster