As you will have gathered, there was an emergency last week at one of the practices I assist. I wasn't in the office when the doctor called in to get help with the OD update, but I was listening on the phone. After navigating past our overzealous firewall, we were told that our Linux setup was all wrong, since it used MyISAM for the DB engine. It was a total mystery to me why the engine would have been set to old-n-busted MyISAM. I specifically remembered that I had edited the configuration file exactly as specified, three years ago when I installed OD in the first place. I theorized that perhaps apt had written over my config file, which it isn't supposed to do, but which I certainly have heard of it doing. "Yeah that must have been it!"
Over the weekend the firewall was fixed. This evening was able to get over to the practice to try again. Wow, the config file does have MyISAM! Confusion! Then I visited the OD Linux page and saw that yes I had done as I was told; that page actually recommends MyISAM. So, at some point between v15 and v17, OD decided to use the modern database engine that mysql has used for years. That's great! Still, this page should be updated. Also, in order to support people who only did as they were told, would it be so hard to drop something like the following at the beginning of the database update scripts?
Code: Select all
SELECT CONCAT('ALTER TABLE ',TABLE_NAME,' ENGINE=InnoDB;') FROM information_schema.TABLES
WHERE ENGINE='MyISAM'
AND table_schema = 'opendental';
Cheers to the support people who stayed late tonight!