mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Doc: Python's control flow construct is try/except not try/catch.

Browse Source 
Very ancient thinko, dating evidently to 22690719e.
Spotted by gweatherby.

Discussion: https://postgr.es/m/170423637139.1288848.11840082988774620003@wrigleys.postgresql.org
This commit is contained in:
Tom Lane 2024-01-03 12:22:00 -05:00
parent 8d4e8b7468
commit 490dee7428
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/sgml/plpython.sgml
View File

@ -1323,7 +1323,7 @@ plan = plpy.prepare("INSERT INTO operations (result) VALUES ($1)", ["text"])
plpy.execute(plan, [result]) plpy.execute(plan, [result])
$$ LANGUAGE plpythonu; $$ LANGUAGE plpythonu;
</programlisting> </programlisting>
Note that the use of <literal>try/catch</literal> is still Note that the use of <literal>try</literal>/<literal>except</literal> is still
required. Otherwise the exception would propagate to the top of required. Otherwise the exception would propagate to the top of
the Python stack and would cause the whole function to abort with the Python stack and would cause the whole function to abort with
a <productname>PostgreSQL</productname> error, so that the a <productname>PostgreSQL</productname> error, so that the