From: | Matt Miller <mattm(at)epx(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: PL/pgSQL: SELECT INTO EXACT |
Date: | 2005-08-08 21:45:54 |
Message-ID: | 1123537554.3062.69.camel@dbamm01-linux |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Mon, 2005-08-08 at 17:18 -0400, Tom Lane wrote:
> Matt Miller <mattm(at)epx(dot)com> writes:
> > On Fri, 2005-07-29 at 17:52 -0400, Tom Lane wrote:
> >> I dislike the choice of "EXACT", too, as it (a) adds a new reserved word
> >> and (b) doesn't seem to convey quite what is happening anyway. Not sure
> >> about a better word though ... anyone?
>
> > I can attach a patch that supports [EXACT | NOEXACT].
>
> Somehow, proposing two new reserved words instead of one doesn't seem
> very responsive to my gripe :-(.
My intention was to introduce the idea that the current behavior should
be changed, and to then suggest a path that eventually eliminates all
the new reserved words.
> If you think that this should be a global option instead of a
> per-statement one, something like the (undocumented) #option hack might
> be a good way to specify it; that would give it per-function scope,
> which seems reasonable.
>
> create function myfn(...) returns ... as $$
> #option select_into_1_row
> declare ...
> $$ language plpgsql;
>
Thanks, I'll take a look at this.
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2005-08-08 21:51:13 | Re: Simplifying wal_sync_method |
Previous Message | Bruce Momjian | 2005-08-08 21:44:15 | Re: Simplifying wal_sync_method |
From | Date | Subject | |
---|---|---|---|
Next Message | Satoshi Nagayasu | 2005-08-08 22:59:39 | Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items) |
Previous Message | Tom Lane | 2005-08-08 21:18:53 | Re: PL/pgSQL: SELECT INTO EXACT |