diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2010-11-09 11:00:56 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2010-11-09 11:05:37 -0300 |
| commit | e55e4c9ced485b44be9e100bbe54546a3272ddae (patch) | |
| tree | 27dbbbf6727456795516f2a3ec7e66c1b939760f | |
| parent | c6c67505e4b7dc4951a149493882dd2debe0766c (diff) | |
plpython has plpy.Error instead of plpy.ERROR
Author: Marti Raudsepp <marti@juffo.org>
| -rw-r--r-- | doc/src/sgml/plpython.sgml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml index aa7804d9bb3..daefc583f3b 100644 --- a/doc/src/sgml/plpython.sgml +++ b/doc/src/sgml/plpython.sgml @@ -954,8 +954,8 @@ $$ LANGUAGE plpythonu; <function>plpy.fatal</function> actually raise a Python exception which, if uncaught, propagates out to the calling query, causing the current transaction or subtransaction to be aborted. - <literal>raise plpy.ERROR(<replaceable>msg</>)</literal> and - <literal>raise plpy.FATAL(<replaceable>msg</>)</literal> are + <literal>raise plpy.Error(<replaceable>msg</>)</literal> and + <literal>raise plpy.Fatal(<replaceable>msg</>)</literal> are equivalent to calling <function>plpy.error</function> and <function>plpy.fatal</function>, respectively. |