| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Josh Kupershmidt <schmiddy(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Documenting removal of nonnullvalue() and friends |
| Date: | 2010-10-14 13:58:28 |
| Message-ID: | 1287064708.9532.3.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On tor, 2010-10-14 at 08:50 -0400, Robert Haas wrote:
> Still, I don't think it would be unreasonable to add a note to the
> prior-release documentation saying - hey, these functions exist. They
> are for internal use only, and do not exist in later versions. Don't
> use 'em. Now, how many people will actually see that note? Probably
> not many. But it wouldn't bother me to have it there.
Just like there is a philosophical argument against changing the release
notes after the release, there is an argument against changing a past
release to "retroactively predict" how future releases behave. We have
made exceptions to both points on occasion, but usually only for
critical upgrade-related issues.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2010-10-14 14:00:06 | Re: Documenting removal of nonnullvalue() and friends |
| Previous Message | Robert Haas | 2010-10-14 12:50:07 | Re: Documenting removal of nonnullvalue() and friends |