Re: How does somebody upgrade to roundup 2.0 if using mysql?
Ralf Schlatterbeck <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.devel |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Jun 01, 2020 at 10:04:32PM -0400, John P. Rouillard wrote: > It looks like we support using ~/.my.cnf to set default character sets > using .my.cnf defined using [rdbms] read_default_file. Do you know of > the top of your head if the config.ini setting for default charset > takes effect or if the ~/.my.cnf file takes effect? I think it would, yes. > Also do you have one of these? That may explain why you were seeing an > issue but nothing in CI was seeing it. No that was one of the first things I checked. > Also Joseph and Ralf, does > https://issues.roundup-tracker.org/issue1194126 still apply? I don't entirely understand the part about subselects in filter. We *are* using subselects for the logic expressions on multilinks. At the time this was implemented mysql did not support subselects and, yes, this could be fixed. Since I'm not using mysql *and* the logic expressions on multilinks (remember, the values -1 and smaller are used for an operator language to formulate queries with and, or, not on multilinks) don't have a regression test, I'm reluctant to fix this. At least a test should be implemented first. > >> >> 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 > > Yeah, still trying to get things to play well here. OK, let us know how to reproduce this. 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]