| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Matt Miller <mattm(at)epx(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [PATCHES] PL/pgSQL: #option select_into_1_row (was SELECT INTO |
| Date: | 2006-03-21 03:23:36 |
| Message-ID: | 200603210323.k2L3NaA14699@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Matt Miller wrote:
> On Mon, 2005-08-08 at 17:18 -0400, Tom Lane wrote:
> > 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;
>
> Attached is a patch that implements the "#option select_into_1_row"
> directive as suggested.
Are we agreed this is the way we want to control this?
--
Bruce Momjian http://candle.pha.pa.us
SRA OSS, Inc. http://www.sraoss.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-03-21 03:28:21 | Re: obtaining row locking information |
| Previous Message | Bruce Momjian | 2006-03-21 01:58:22 | Re: Additional current timestamp values |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-21 03:30:39 | Re: [PATCHES] PL/pgSQL: #option select_into_1_row (was SELECT INTO |
| Previous Message | Bruce Momjian | 2006-03-21 01:58:22 | Re: Additional current timestamp values |