rubberduck

Comments

• Ha, look here... https://mariadb.com/kb/en/mariadb-vs-mysql-compatibility/#incompatibilities-between-mariadb-55-and-mysql-55 I think the stock mariadb version in rhel (5.5.x) may have some compatibility issues with mysql 5.5. So I should either go …

  in "An evolution has not been applied properly." error after 3.5.4 upgrade Comment by rubberduck May 2020
• ok, Tomorrow I will deploy a clean virtual 3.5.3 server (everything is puppetised here) and see if that upgrades well. If it does not, I can try the same deployment but with mysql 5.7.30 to see if there is any difference. Thankfully this was a test…

  in "An evolution has not been applied properly." error after 3.5.4 upgrade Comment by rubberduck May 2020
• Hi Kristian, Thanks for the reply (and Jatos of course :-) ) We are running it on rhel7. I have mariadb 5.5.65 installed, for now on the same machine, so db.default.url="jdbc:mysql://localhost/jatos?characterEncoding=UTF-8&useSSL=false&…

  in "An evolution has not been applied properly." error after 3.5.4 upgrade Comment by rubberduck May 2020