-
- Downloads
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.
Showing
- src/pl/plpython/expected/plpython_types.out 61 additions, 0 deletionssrc/pl/plpython/expected/plpython_types.out
- src/pl/plpython/expected/plpython_types_3.out 90 additions, 29 deletionssrc/pl/plpython/expected/plpython_types_3.out
- src/pl/plpython/plpython.c 5 additions, 40 deletionssrc/pl/plpython/plpython.c
- src/pl/plpython/sql/plpython_types.sql 50 additions, 0 deletionssrc/pl/plpython/sql/plpython_types.sql
Loading
Please register or sign in to comment