mirror of
https://github.com/postgres/postgres.git
synced 2026-02-15 00:33:54 -05:00
3ab8b7fa6f
Before, PL/Python converted data between SQL and Python by going through a C string representation. This broke for bytea in two ways: - On input (function parameters), you would get a Python string that contains bytea's particular external representation with backslashes etc., instead of a sequence of bytes, which is what you would expect in a Python environment. This problem is exacerbated by the new bytea output format. - On output (function return value), null bytes in the Python string would cause truncation before the data gets stored into a bytea datum. This is now fixed by converting directly between the PostgreSQL datum and the Python representation. The required generalized infrastructure also allows for other improvements in passing: - When returning a boolean value, the SQL datum is now true if and only if Python considers the value that was passed out of the PL/Python function to be true. Previously, this determination was left to the boolean data type input function. So, now returning 'foo' results in true, because Python considers it true, rather than false because PostgreSQL considers it false. - On input, we can convert the integer and float types directly to their Python equivalents without having to go through an intermediate string representation. original patch by Caleb Welton, with updates by myself |
||
|---|---|---|
| .. | ||
| plpython_drop.sql | ||
| plpython_error.sql | ||
| plpython_global.sql | ||
| plpython_import.sql | ||
| plpython_newline.sql | ||
| plpython_params.sql | ||
| plpython_populate.sql | ||
| plpython_record.sql | ||
| plpython_schema.sql | ||
| plpython_setof.sql | ||
| plpython_spi.sql | ||
| plpython_test.sql | ||
| plpython_trigger.sql | ||
| plpython_types.sql | ||
| plpython_unicode.sql | ||
| plpython_void.sql | ||