Re: Documenting removal of nonnullvalue() and friends

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Kupershmidt <schmiddy(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org
Subject: Re: Documenting removal of nonnullvalue() and friends
Date: 2010-11-16 22:24:34
Message-ID: 1289946274.31200.74.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On lör, 2010-10-16 at 10:28 -0400, Tom Lane wrote:
> I've occasionally toyed with the idea of moving all non-public
> functions
> into a separate schema, say "pg_internal", which wouldn't be in the
> standard search path (and thus ordinary \df wouldn't see it). That
> would be nice from a cleanliness standpoint, but there are downsides
> too.

Another thing we could do at least for new functions is to name them
starting with an underscore (or two).

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Greg Smith 2010-11-19 03:29:50 Re: [PATCH] Fix documentation about PL/Python exception handling
Previous Message Marti Raudsepp 2010-11-15 21:21:13 Re: [PATCH] Fix documentation about PL/Python exception handling