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

On Tue, May 26, 2020 at 12:40:03PM -0400, John P. Rouillard wrote:
> >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.
> 
> Well IIUC we have been doing that all along with roundup. This would
> just continue the (very broken) practice.

We already have a case where the indexer isn't working. I expect more
and more issues cropping up, so better fix sooner than later.

> >setups where the backend might use UTF-8.
> 
> So when the database was created, somebody explicitly ran a mysql
> command to change the encoding from latin1 to some other setting?

Yes, I guess that users of a language that routinely uses multi-byte
encoding would probably have their database set up with non-latin1. But
if not we're facing the same problems.

> >> 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.
> 
> Sorry, I wasn't clear. It was a roundup-admin 2.0 export/import which
> is architecture independent.

Ouch. That should be investigated in more detail

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]