public inbox for [email protected]
help / color / mirror / Atom feedFrom: Marti Raudsepp <[email protected]>
To: Marko Tiikkaja <[email protected]>
Cc: PG Docs <[email protected]>
Subject: Re: PL/PgSQL INTO (used to be BUG #8870)
Date: Fri, 1 Aug 2014 15:57:10 +0300
Message-ID: <CABRT9RDPtCD8fqy_pCeD2siafsJF=Z3+C_Y86h-WvJQV02iehg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CABRT9RBLCyy0eHBpOneaAke_A3hVvnNwMyvhKiJRB=3C5x83DQ@mail.gmail.com>
<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>
On Fri, Aug 1, 2014 at 2:43 PM, Marko Tiikkaja <[email protected]> wrote:
> But the claim about "exactly matching" data types is completely bogus, too
My bad. I remember having a hard time with matching data types in
PL/pgSQL in one instance, but turns out that was with RETURN QUERY,
not INTO.
Anyway, I'd prefer adding an explicit warning about the non-strict
behavior. How about:
"The number of columns returned by the query is not checked to match
target variables. Superfluous target variables are assigned the value
NULL.
When a record variable is the target, it automatically
configures itself to the row type of the query result columns."
Regards,
Marti
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
view thread (4+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: PL/PgSQL INTO (used to be BUG #8870)
In-Reply-To: <CABRT9RDPtCD8fqy_pCeD2siafsJF=Z3+C_Y86h-WvJQV02iehg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox