[SAC] [OSGeo] #2081: wp: Data corruption on profile save (encoding problem)
OSGeo
trac_osgeo at osgeo.org
Fri Jan 12 17:54:23 PST 2018
#2081: wp: Data corruption on profile save (encoding problem)
---------------------+-----------------------
Reporter: marisn | Owner: webcom@…
Type: defect | Status: new
Priority: normal | Milestone:
Component: WebSite | Resolution:
Keywords: |
---------------------+-----------------------
Comment (by robe):
I reloaded the data from https://staging.www.osgeo.org to
https://staging2.www.osgeo.org
and then converted all the tables and columns to utf8mb4 character set and
utfmb4_unicode_ci collation.
After that I tried the above two examples, and the input text is no longer
mangled.
I went with utf8mb4 because MYSQL utf8 (is a 3 byte character code system
so doesn't support all utf8). The downside is utf8mb4 doesn't work with
really old mysql drivers or mysql servers.
I did a quick test on staging.www.osgeo.org to quickly confirm it supports
utf8mb4.
Anyrate I'm hesitate to make the change on staging.www.osgeo.org, without
people looking at staging2 to confirm nothing got mangled in the process.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2081#comment:4>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
More information about the Sac
mailing list