Re: [PATCH] Fix documentation about PL/Python exception handling - Mailing list pgsql-docs

From Greg Smith
Subject Re: [PATCH] Fix documentation about PL/Python exception handling
Date
Msg-id 4CE5EF2E.6040108@2ndquadrant.com
Whole thread Raw
In response to Re: [PATCH] Fix documentation about PL/Python exception handling  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] Fix documentation about PL/Python exception handling
List 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@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services and Support        www.2ndQuadrant.us



pgsql-docs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Documenting removal of nonnullvalue() and friends
Next
From: Marti Raudsepp
Date:
Subject: Re: [PATCH] Fix documentation about PL/Python exception handling