Re: Assignment to composite type variable fails inside function but running query separately yields correct type & value ? - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: Assignment to composite type variable fails inside function but running query separately yields correct type & value ?
Date
Msg-id CAKFQuwapumtrdWSWZXNGoLxqC8eeseeZx1H-EgB3C3Qor+y_-g@mail.gmail.com
Whole thread Raw
In response to Assignment to composite type variable fails inside function but running query separately yields correct type & value ?  (Tobias Gierke <tobias.gierke@code-sourcery.de>)
Responses Re: Assignment to composite type variable fails inside function but running query separately yields correct type & value ?  (Tobias Gierke <tobias.gierke@code-sourcery.de>)
List pgsql-bugs
On Tue, Jan 26, 2021 at 5:56 AM Tobias Gierke <tobias.gierke@code-sourcery.de> wrote:
voip$#         SELECT (t1.a_major, t1.a_minor )::version_num INTO _myid

Bug or feature ?


Feature.  The first column of the select result gets placed into the first field of _myid, the second column of the select result gets placed into the second field of _myid.  This is how assignment to row-typed variables (and record-typed too) works in pl/pgsql.

David J.

pgsql-bugs by date:

Previous
From: Tobias Gierke
Date:
Subject: Assignment to composite type variable fails inside function but running query separately yields correct type & value ?
Next
From: Tobias Gierke
Date:
Subject: Re: Assignment to composite type variable fails inside function but running query separately yields correct type & value ?