Re: plpgsql mixing variable in SELECT INTO ?

From: Jean-Luc Lachance <jllachan(at)nsd(dot)ca>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ben-Nes Michael <miki(at)canaan(dot)co(dot)il>, postgresql <pgsql-general(at)postgresql(dot)org>
Subject: Re: plpgsql mixing variable in SELECT INTO ?
Date: 2003-03-04 19:56:05
Message-ID: 3E6504D5.46B48790@nsd.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Maybe he is looking at a shorthand for assigning a row variable to an
other...

Tom Lane wrote:
>
> "Ben-Nes Michael" <miki(at)canaan(dot)co(dot)il> writes:
> > 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 ?
>
> Certainly you can. But when you assign into a row variable, you have to
> provide all the row variable's columns, in order. How else would you
> expect it to work?
>
> > Also its quite strange that my code worked in 7.3.1-
>
> I don't believe it.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Sabino Mullane 2003-03-04 19:59:39 Mailing lists still points to a non-existent page
Previous Message Andrew Sullivan 2003-03-04 19:54:45 Re: pg_ctl -m fast failing?