pgsql: Docs: be explicit about datatype matching for lead/lag functions - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Docs: be explicit about datatype matching for lead/lag functions
Date
Msg-id E1ZUNP1-0005tP-CB@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Docs: be explicit about datatype matching for lead/lag functions.

The default argument, if given, has to be of exactly the same datatype
as the first argument; but this was not stated in so many words, and
the error message you get about it might not lead your thought in the
right direction.  Per bug #13587 from Robert McGehee.

A quick scan says that these are the only two built-in functions with two
anyelement arguments and no other polymorphic arguments.  There are plenty
of cases of, eg, anyarray and anyelement, but those seem less likely to
confuse.  For instance this doesn't seem terribly hard to figure out:
"function array_remove(integer[], numeric) does not exist".  So I've
contented myself with fixing these two cases.

Branch
------
REL9_2_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/8cffc4f5bdfbd41e27680fca27d82ae939cdeda8

Modified Files
--------------
doc/src/sgml/func.sgml |   16 ++++++++++------
1 file changed, 10 insertions(+), 6 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Docs: be explicit about datatype matching for lead/lag functions
Next
From: Tom Lane
Date:
Subject: pgsql: Docs: be explicit about datatype matching for lead/lag functions