From: | "Ben-Nes Michael" <miki(at)canaan(dot)co(dot)il> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "postgresql" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: plpgsql mixing variable in SELECT INTO ? |
Date: | 2003-03-04 17:22:01 |
Message-ID: | 004701c2e272$91daa610$aa0f5ac2@canaan.co.il |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi
You mean I cant use the full power of the SELECT as mentioned in the manual
and when using SELECT INTO I must use * and I can refine my query to some of
the fields ?
Also its quite strange that my code worked in 7.3.1-
Cheers
--------------------------
Canaan Surfing Ltd.
Internet Service Providers
Ben-Nes Michael - Manager
Tel: 972-4-6991122
Fax: 972-4-6990098
http://sites.canaan.co.il
--------------------------
----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Ben-Nes Michael" <miki(at)canaan(dot)co(dot)il>
Cc: "postgresql" <pgsql-general(at)postgresql(dot)org>
Sent: Tuesday, March 04, 2003 5:16 PM
Subject: Re: [GENERAL] plpgsql mixing variable in SELECT INTO ?
> "Ben-Nes Michael" <miki(at)canaan(dot)co(dot)il> writes:
> > so it seems that order does matter and one canot ommit the first field
in
> > the table structure.
>
> What's surprising about that? That's exactly how it *should* work, IMHO.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-03-04 17:45:49 | Re: plpgsql mixing variable in SELECT INTO ? |
Previous Message | Josh Berkus | 2003-03-04 17:18:07 | pg_ctl -m fast failing? |