On Fri, Aug 1, 2014 at 2:43 PM, Marko Tiikkaja 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 ad
On 8/1/14 1:33 PM, Marti Raudsepp wrote:
On Fri, Aug 1, 2014 at 12:34 AM, Marko Tiikkaja wrote:
Here's a patch removing the incorrect part.
I can see how this doc statement can be misunderstood, but I think the
claims are actually about data types, not the number of columns in the
INTO list.
On Fri, Aug 1, 2014 at 12:34 AM, Marko Tiikkaja wrote:
> Here's a patch removing the incorrect part.
I can see how this doc statement can be misunderstood, but I think the
claims are actually about data types, not the number of columns in the
INTO list.
I think clarifying the number of columns q
Hi,
As discussed in #8870, the docs make unfounded claims on INTO. Here's a
patch removing the incorrect part.
.marko
*** a/doc/src/sgml/plpgsql.sgml
--- b/doc/src/sgml/plpgsql.sgml
***
*** 1023,1032 DELETE ... RETURNING expressions
INTO STRIC
! If a r
