From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, pgsql-hackers(at)postgreSQL(dot)org, pgsql-sql(at)postgreSQL(dot)org |
Subject: | Re: PL/pgsql EXECUTE 'SELECT INTO ...' |
Date: | 2001-02-08 19:49:26 |
Message-ID: | 12696.981661766@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> I am inclined to keep our options open by forbidding EXECUTE 'SELECT
>> INTO ...' for now. That's more than a tad annoying, because that leaves
>> no useful way to do a dynamically-built SELECT, but if we don't forbid
>> it I think we'll regret it later.
> You can always use CREATE TABLE AS.
Does SPI_exec() support that? (Tries it ... seems to work ...)
Cool. OK, we have the bases covered then; there's no need to allow
SELECT INTO inside EXECUTE until we can make it work as expected.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-02-08 19:49:55 | Re: Syslog and pg_options (for RPMs) |
Previous Message | Tom Lane | 2001-02-08 19:43:33 | Re: Syslog and pg_options (for RPMs) |
From | Date | Subject | |
---|---|---|---|
Next Message | Jelle Ouwerkerk | 2001-02-08 22:28:59 | fetching the id of a new row |
Previous Message | Peter Eisentraut | 2001-02-08 19:37:16 | Re: PL/pgsql EXECUTE 'SELECT INTO ...' |