Re: mysqlIndexerTest.test_unicode fails for me
"John P. Rouillard" <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Ralf: In message <[email protected]>, Ralf Schlatterbeck writes: >On Thu, Apr 30, 2020 at 12:52:38PM +0000, Joseph Myers wrote: >> >> That condition was so that a database created with older Roundup, with >> Python 2, continues to work properly with newer Roundup, with Python 2. >> (I couldn't get such a database to work with Python 3, hence the >> documentation of needing to export and import when moving to Python 3 with >> MySQL.) > >I see, how about making the database encoding for mysql a config-item >which defaults to utf-8 and stating in the documentation for people >upgrading that they have to set this if they have a different database >encoding? I'd voluteer to do that if someone looks over my documentation >:-) I would suggest three values for the setting if we go this route: default latin1 utf8 default chooses utf8 if python3, latin1 if python2 and is the default value for the setting. The admin can explicitly choose one of the other two which are the default values for older or newer mysql libraries/servers. I don't think there is value in permitting any other values for the charset. Thoughts? -- -- rouilj John Rouillard =========================================================================== My employers don't acknowledge my existence much less my opinions.