| From: | ncm(at)zembu(dot)com (Nathan Myers) |
|---|---|
| To: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: PL/pgsql EXECUTE 'SELECT INTO ...' |
| Date: | 2001-02-08 05:33:47 |
| Message-ID: | 20010207213347.A19999@store.zembu.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
On Wed, Feb 07, 2001 at 10:15:02PM -0500, Tom Lane wrote:
> I have looked a little bit at what it'd take to make SELECT INTO inside
> an EXECUTE work the same as it does in plain plpgsql ...
> If we do nothing now, and then implement this feature in 7.2, we will
> have a backwards compatibility problem: EXECUTE 'SELECT INTO ...'
> will completely change in meaning.
>
> I am inclined to keep our options open by forbidding EXECUTE 'SELECT
> INTO ...' for now. ... if [not] I think we'll regret it later.
I agree, disable it. But put a backpatch into contrib along with
a reference to this last e-mail. Anybody who cares enough can
apply the patch, and will be prepared for the incompatibility.
Nathan Myers
ncm(at)zembu(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2001-02-08 09:17:34 | AW: AW: timestamp in pg_dump |
| Previous Message | Bruce Momjian | 2001-02-08 04:57:32 | Re: Re: [PATCHES] A Sparc/Linux patch (for 7.1), and a Linux rc.d/init.d script.... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Miyabara-McCaskey | 2001-02-08 06:22:17 | RE: FATAL 1: btree: items are out of order (leftmost 0, stack 48, update 2) |
| Previous Message | manjul katare | 2001-02-08 04:57:26 | sql query |