Am 23.11.2015 um 11:42 schrieb D'Arcy J.M. Cain:
Right. I have actually started updating my production databases but not my test one. I could easily drop and recreate it but first we should decide if it should work with ASCII databases. Many people will still have them. Are we going to require UTF8 for 5.x? If so then I will go ahead and upgrade. If not then we should query the database type and skip tests if they don't apply.
This kept bothering me, so I have adapted the tests for database with other encodings and added some more heavy testing of unicode issues.
In r614 I also fixed a bug that could have caused the segfaults we sometimes observed when using inserttable with unicode.
Can you try again? Under Linux, all tests are now passing for me in Python 2 and Python 3 for test databases with the following encodings: sql_ascii, iso_8859_1 (latin1), iso_8859_5 (cyrillic), iso_8859_15 (euro) and utf8. Some tests are automatically skipped if the database encoding does not support the tested characters. No tests should be skipped for sql_ascii and utf8 since they can store all characters.
-- Christoph _______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo.cgi/pygresql
