database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-25 01:02:05 +03:00
Code Activity

Spell checking and markup refinement

Browse Source
This commit is contained in:
Peter Eisentraut
2011-05-19 01:14:45 +03:00
parent 0ee391b77a
commit c13dc6402b
37 changed files with 97 additions and 97 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -356,7 +356,7 @@ $$ LANGUAGE plpythonu;
<para>
When the PostgreSQL return type is <type>bytea</type>, the
return value will be converted to a string (Python 2) or bytes
(Python 3) using the respective Python builtins, with the
(Python 3) using the respective Python built-ins, with the
result being converted <type>bytea</type>.
</para>
</listitem>
@ -365,7 +365,7 @@ $$ LANGUAGE plpythonu;
<para>
For all other PostgreSQL return types, the returned Python
value is converted to a string using the Python
builtin <literal>str</literal>, and the result is passed to the
built-in <literal>str</literal>, and the result is passed to the
input function of the PostgreSQL data type.
</para>
@ -1101,7 +1101,7 @@ $$ LANGUAGE plpythonu;
inserted into it. The subtransaction context manager does not
trap errors, it only assures that all database operations executed
inside its scope will be atomically committed or rolled back. A
rollback of the subtransaction block occurrs on any kind of
rollback of the subtransaction block occurs on any kind of
exception exit, not only ones caused by errors originating from
database access. A regular Python exception raised inside an
explicit subtransaction block would also cause the subtransaction