| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | miko(at)idocs(dot)com (Miko O'Sullivan) |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: [BUGS] session variable |
| Date: | 2003-09-17 21:23:05 |
| Message-ID: | 5999.1063833785@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-sql |
miko(at)idocs(dot)com (Miko O'Sullivan) writes:
> Unfortunately in the 7.2.x version I have available, EXECUTE does not
> allow "select into". The docs suggests a technique for using a FOR
> loop to extract information from an EXECUTE, but the technique only
> works for finite set of expected variables, not for arbitrary values.
How do you figure that? AFAICS "FOR" with a record variable as target
will cover any case that SELECT INTO could handle.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Miko O Sullivan | 2003-09-17 21:50:57 | Need more examples (was "session variable") |
| Previous Message | Arthur Ward | 2003-09-17 16:35:26 | Re: plpython (triggers?) and dropped attributes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Miko O Sullivan | 2003-09-17 21:50:57 | Need more examples (was "session variable") |
| Previous Message | Tom Lane | 2003-09-17 21:13:13 | Re: cursors in plpgsql |