[DOCS] plpython docs should say 'plpy.Error' instead of ERROR

2010-11-09 Thread Marti Raudsepp
Currently the PL/Python documentation claims that: "raise plpy.ERROR(msg) and raise plpy.FATAL(msg) are equivalent to calling plpy.error and plpy.fatal, respectively" However, the actual names are Error and Fatal, not ERROR or FATAL (Python is case-sensitive). Patch to fix documentation attached.

Re: [DOCS] plpython docs should say 'plpy.Error' instead of ERROR

2010-11-09 Thread Alvaro Herrera
Excerpts from Marti Raudsepp's message of mar nov 09 07:21:54 -0300 2010: > Currently the PL/Python documentation claims that: > "raise plpy.ERROR(msg) and raise plpy.FATAL(msg) are equivalent to > calling plpy.error and plpy.fatal, respectively" > > However, the actual names are Error and Fatal,

[DOCS] [PATCH] Fix documentation about PL/Python exception handling

2010-11-09 Thread Marti Raudsepp
Hi lists, It seems that PL/Python exception functions (plpy.error, plpy.fatal) and exception types (plpy.Error, plpy.Fatal) have never worked as documented, and the behavior is quite surprising. This is an attempt at properly documenting the current semantics. I tested these behaviors on PostgreS