From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Documenting removal of nonnullvalue() and friends |
Date: | 2010-10-14 14:38:11 |
Message-ID: | 18056.1287067091@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Josh Kupershmidt <schmiddy(at)gmail(dot)com> writes:
> I'm curious now, though: are there any other functions which we're
> leaving intentionally undocumented?
Practically all the functions underlying operators are undocumented, eg
int4pl(int, int). (If you consider IS NOT NULL to be an operator, then
nonnullvalue is exactly one of those.) It's possible for people to use
those directly but it's discouraged. I do *not* want to add them to the
docs, because (a) I do *not* want people to use them directly and (b)
there are a hell of a lot of them, so the docs would get much much
longer with no actual added value.
Perhaps what we should really add to the docs is a statement that use of
undocumented functions is deprecated and we will not be responsible when
your code breaks because one of those is changed or removed.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Jurd | 2010-10-14 15:24:17 | Re: [HACKERS] Docs for archive_cleanup_command are poor |
Previous Message | Tom Lane | 2010-10-14 14:33:26 | Re: Documenting removal of nonnullvalue() and friends |