I recently transferred my GnuCash data from another computer to my new one. In the process, I switched from a MySQL instance in a WAMP installation on the old computer to a stand-alone MariaDB install on the new computer. On the old computer, I saved the data in xml format, then opened that file on the new computer, finally saving in sql format. I noticed that my dark theme and saved reports didn't follow during the move, but another helpful person here pointed me to the correct documentation which corrected both of those issues. Neither seem related to the accounting data itself.
So, all was well and I had logged in and out several times making sure the password was recorded correctly in a keyboard macro for easier access. I have not done any data entry since the move. The old computer and the original transfer file is still available. Nevertheless, the impression I was given was that, going forward, MariaDB was the preferred sql back end because "we switched the connectors in the Gnucash-built bundles and in flatpak to MariaDB's because MySQL discontinued their C ones and the C++ one won't work with libdbi". Today I try to login to actually do work in GnuCash for the first time on the new computer and I get the following message: *The server at URL mysql://root@localhost/gnucash experienced an error or encountered bad or corrupt data.* I have verified the password is correct, restarted the PC, and looked at the data from HeidiSQL and can see no issue with anything. This freaks me out as NEVER did this EVER happen with MySQL on the old computer. Is there a resolution to this? Must I start the migration all over again? How do I regain confidence in the SQL back end when this happens so quickly after changing db engines? Thanks. Tom Middleton, WI USA _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.