| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Marti Raudsepp <marti(at)juffo(dot)org>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Fix documentation about PL/Python exception handling |
| Date: | 2010-11-19 03:29:50 |
| Message-ID: | 4CE5EF2E.6040108@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Tom Lane wrote:
> Hmmm ... I'm less than excited about documenting agreed-to-be-broken
> behavior in exquisite detail. Doing so will just encourage people to
> rely on it. It's particularly unfriendly to document it in detail
> without pointing out that it's likely to change.
>
> My inclination is to forget about these doc changes and spend our time
> on fixing the behavior instead.
>
The open question for this one then is the right way for exceptions to
act. Marti, since you've looked at this a bit already, any thoughts on
what that should look like? You initially commented that what happens
was surprising, but I'm not clear on what you expected to happen instead.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services and Support www.2ndQuadrant.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marti Raudsepp | 2010-11-19 08:35:11 | Re: [PATCH] Fix documentation about PL/Python exception handling |
| Previous Message | Peter Eisentraut | 2010-11-16 22:24:34 | Re: Documenting removal of nonnullvalue() and friends |