postgresql/src/pl/plpython/expected/README

Guide to alternative expected files:

plpython_error_2.out		Python 2.2, 2.3, 2.4
plpython_error.out			Python 2.5, 2.6

plpython_unicode.out		any version, when server encoding != SQL_ASCII; else ...
plpython_unicode_2.out		Python 2.2
plpython_unicode_3.out		Python 2.3, 2.4
plpython_unicode_5.out		Python 2.5, 2.6
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:`

			`plpython_error_2.out Python 2.2, 2.3, 2.4`
			`plpython_error.out Python 2.5, 2.6`
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.out any version, when server encoding != SQL_ASCII; else ...`
			`plpython_unicode_2.out Python 2.2`
			`plpython_unicode_3.out Python 2.3, 2.4`
			`plpython_unicode_5.out Python 2.5, 2.6`