Re: plpgsql mixing variable in SELECT INTO ?
От | Ben-Nes Michael |
---|---|
Тема | Re: plpgsql mixing variable in SELECT INTO ? |
Дата | |
Msg-id | 004701c2e272$91daa610$aa0f5ac2@canaan.co.il обсуждение исходный текст |
Ответ на | plpgsql mixing variable in SELECT INTO ? ("Ben-Nes Michael" <miki@canaan.co.il>) |
Ответы |
Re: plpgsql mixing variable in SELECT INTO ?
|
Список | 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@sss.pgh.pa.us> To: "Ben-Nes Michael" <miki@canaan.co.il> Cc: "postgresql" <pgsql-general@postgresql.org> Sent: Tuesday, March 04, 2003 5:16 PM Subject: Re: [GENERAL] plpgsql mixing variable in SELECT INTO ? > "Ben-Nes Michael" <miki@canaan.co.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 >
В списке pgsql-general по дате отправления: