Thanks to visit codestin.com
Credit goes to anoncvs.postgresql.org

CVS log for pgsql/src/pl/plpython/expected/plpython_unicode_3.out

[BACK] Up to [PostgreSQL CVS Repository] / pgsql / src / pl / plpython / expected

Request diff between arbitrary revisions - Display revisions graphically


Keyword substitution: kv
Default branch: MAIN


Revision 1.5: download - view: text, markup, annotated - select for diffs
Sat Jan 16 11:03:51 2010 UTC (15 years, 8 months ago) by petere
Branches: MAIN
CVS tags: REL9_1_ALPHA1, REL9_0_STABLE, REL9_0_RC1, REL9_0_BETA4, REL9_0_BETA3, REL9_0_BETA2, REL9_0_BETA1, REL9_0_ALPHA5_BRANCH, REL9_0_ALPHA5, REL9_0_ALPHA4_BRANCH, REL9_0_ALPHA4, REL9_0_0, HEAD
Diff to: previous 1.4: preferred, colored
Changes since revision 1.4: +3 -3 lines
Improved printing of Python exceptions in PL/Python

Mimic the Python interpreter's own logic for printing exceptions instead
of just using the straight str() call, so that
you get

    plpy.SPIError

instead of

    <class 'plpy.SPIError'>

and for built-in exceptions merely

    UnicodeEncodeError

Besides looking better this cuts down on the endless version differences
in the regression test expected files.

Revision 1.4: download - view: text, markup, annotated - select for diffs
Sun Sep 13 22:07:06 2009 UTC (16 years ago) by petere
Branches: MAIN
CVS tags: REL8_5_ALPHA3_BRANCH, REL8_5_ALPHA3, REL8_5_ALPHA2_BRANCH, REL8_5_ALPHA2
Diff to: previous 1.3: preferred, colored
Changes since revision 1.3: +28 -21 lines
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.

Revision 1.3
Sat Sep 12 22:13:12 2009 UTC (16 years ago) by petere
Branches: MAIN
FILE REMOVED
Changes since revision 1.2: +0 -0 lines
Add Unicode support in PL/Python

PL/Python now accepts Unicode objects where it previously only accepted string
objects (for example, as return value).  Unicode objects are converted to the
PostgreSQL server encoding as necessary.

This change is also necessary for future Python 3 support, which treats all
strings as Unicode objects.

Since this removes the error conditions that the plpython_unicode test file
tested for, the alternative result files are no longer necessary.

Revision 1.2: download - view: text, markup, annotated - select for diffs
Tue Aug 25 12:44:59 2009 UTC (16 years ago) by petere
Branches: MAIN
Diff to: previous 1.1: preferred, colored
Changes since revision 1.1: +6 -4 lines
Enhanced error context support in PL/Python

Extract the "while creating return value" and "while modifying trigger
row" parts of some error messages into another layer of error context.
This will simplify the upcoming patch to improve data type support, but
it can stand on its own.

Revision 1.1: download - view: text, markup, annotated - select for diffs
Wed Aug 12 16:37:25 2009 UTC (16 years, 1 month ago) by petere
Branches: MAIN
CVS tags: REL8_5_ALPHA1_BRANCH, REL8_5_ALPHA1
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.

Diff request

This form allows you to request diffs between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.

Log view options

PostgreSQL CVSweb <[email protected]>