From: | marcelo <marcelo(dot)nicolet(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Select into table%ROWTYPE failed |
Date: | 2018-09-18 18:38:11 |
Message-ID: | 14186ea7-288e-c011-616c-56cd577793cd@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ohh, you are right!
Thank you!
On 18/09/2018 14:10 , Tom Lane wrote:
> marcelo <marcelo(dot)nicolet(at)gmail(dot)com> writes:
>> What was wrong in the first approach?
> plpgsql's "SELECT INTO" expects a one-for-one match between the output
> columns of the SELECT and the columns of the INTO destination. So I'd
> expect something like this to work:
>
> DECLARE
> ranger billnumberrange%ROWTYPE;
> BEGIN
> SELECT * FROM billnumberrange WHERE ... INTO ranger;
>
> Your example clearly wasn't selecting all the columns, and it
> wasn't clear whether you paid any attention to column ordering;
> but both of those matter.
>
> regards, tom lane
>
---
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.
https://www.avast.com/antivirus
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2018-09-18 18:40:16 | Re: Code of Conduct |
Previous Message | VENKTESH GUTTEDAR | 2018-09-18 18:37:37 | [GENERAL] optimising the pl/pgsql function |