Files
postgresql/src/pl/plpython/expected
Peter Eisentraut 12c2f2f66c Use data-type specific conversion functions also in plpy.execute
In PLy_spi_execute_plan, use the data-type specific Python-to-PostgreSQL
conversion function instead of passing everything through InputFunctionCall
as a string.  The equivalent fix was already done months ago for function
parameters and return values, but this other gateway between Python and
PostgreSQL was apparently forgotten.  As a result, data types that need
special treatment, such as bytea, would misbehave when used with
plpy.execute.
2010-03-18 13:23:57 +00:00
..
2010-01-22 15:45:15 +00:00
2010-01-22 15:45:15 +00:00
2009-11-03 11:05:03 +00:00

Guide to alternative expected files:

plpython_unicode.out		any version, when server encoding != SQL_ASCII and client encoding = UTF8; else ...
plpython_unicode_0.out		any version, when server encoding != SQL_ASCII and client encoding != UTF8; else ...
plpython_unicode_2.out		Python 2.2
plpython_unicode_3.out		Python 2.3, 2.4, 2.5, 2.6

plpython_types_3.out		Python 3.1