| From: | Marti Raudsepp <marti(at)juffo(dot)org> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to> |
| Cc: | PG Docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: PL/PgSQL INTO (used to be BUG #8870) |
| Date: | 2014-08-01 12:57:10 |
| Message-ID: | CABRT9RDPtCD8fqy_pCeD2siafsJF=Z3+C_Y86h-WvJQV02iehg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Fri, Aug 1, 2014 at 2:43 PM, Marko Tiikkaja <marko(at)joh(dot)to> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2014-08-08 23:41:47 | Sample archive_command is still problematic |
| Previous Message | Marko Tiikkaja | 2014-08-01 11:43:44 | Re: PL/PgSQL INTO (used to be BUG #8870) |