Re: How does somebody upgrade to roundup 2.0 if using mysql?

On Tue, May 26, 2020 at 11:35:05AM -0400, John P. Rouillard wrote:
> 
> Is it possible to add a seting (maybe charset = None) to go back to
> the original way of not using a charset. This is obviously not a great
> alternative as we have encodning on encoding, but it provides an
> upgrade path to 2.0 that is compatible with roundup 1.6.
> 
> That at least gives the user the option of retaining the 1.X behavior.

I do not think this is possible: We wrote UTF-8 to a latin1 backend.
Continuing with this setup is a recipe for desaster later on.

> If I understand you correctly, if we have a double encoded database
> utf8 encoded data (generated by roundup) re-encoded as latin1 (by
> mysql), a dump/restore is required.
> 
> I expect this is the state for all roundup 1.x mysql databases. Do you
> expect to have 1.x databases with utf8 encoded data stored as utf8 by
> mysql?

I guess that users with a non-european language will have different
setups where the backend might use UTF-8.

> I will take another shot at getting my development system running
> cleanly again. When I tried to test running mysql on a pi, it was
> problematic. The import of my test db crashed the system 8-).

Hmm, It might be that mysql databases are not binary-compatible between
different processors.

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: [email protected]