postgresql/src/pl/plpython/expected/README

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 through 3.1

plpython_types_3.out		Python 3.1
Split the plpython regression test into test cases arranged by topic, instead of the previous monolithic setup-create-run sequence, that was apparently inherited from a previous test infrastructure, but makes working with the tests and adding new ones weird. 2009-08-12 12:37:26 -04:00			`Guide to alternative expected files:`

Add alternative expected file for unicode test for client encoding not UTF8 2009-10-14 17:42:58 -04:00			`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 ...`
Fix Unicode support in PL/Python Check calls of PyUnicode_AsEncodedString() for NULL return, probably because the encoding name is not known. Add special treatment for SQL_ASCII, which Python definitely does not know. Since using SQL_ASCII produces errors in the regression tests when non-ASCII characters are involved, we have to put back various regression test result variants. 2009-09-13 18:07:06 -04:00			`plpython_unicode_2.out Python 2.2`
Update Python version information 2010-06-12 02:05:48 -04:00			`plpython_unicode_3.out Python 2.3 through 3.1`
Python 3 support in PL/Python Behaves more or less unchanged compared to Python 2, but the new language variant is called plpython3u. Documentation describing the naming scheme is included. 2009-12-15 17:59:55 -05:00
			`plpython_types_3.out Python 3.1`