![]() |
|
InnoDB vs. MyISAM - Printable Version +- ZenphotoCMS Forum (https://forum.zenphoto.org) +-- Forum: Support (https://forum.zenphoto.org/forum-1.html) +--- Forum: General support (https://forum.zenphoto.org/forum-4.html) +--- Thread: InnoDB vs. MyISAM (/thread-12515.html) |
InnoDB vs. MyISAM - rtwingfield - 2016-05-11 After several months of down time, I have installed zenphoto-1.4.12 -- not an upgrade, but a fresh install. Previous version was < zenphoto-1.4.11. There were a lot of other intervening issues,e.g., OS upgrade to FreeBSD v10.2. MySQL to v5.7.10 (now defaults to InnoDB), conversion from AT&T legacy ADSL to U-verse (static IP block), conversion from NetGear FVX538 router to Cisco RV016, ad nauseam. Regardless, I have successfully restored all albums from backup; however, I don't know what to do with the DB table content. As I recall, the previous version of ZenPhoto installed on MyISAM tables. The fresh install created InnoDB style tables. [list] [*]What are the differences in the table schemas? [*]Is there a conversion-mapping system to accomplish such a task? [/list] InnoDB vs. MyISAM - acrylian - 2016-05-12 MyISAM was the former default database engine format MySQL used up to version 5.5, InnoDB is the current. It is actually not Zenphoto setting this up but your MySQL server when creating databases/tables. Zenphoto would work with both (and probably other engines, too). I don't think there is any conversion mapping necessary. All my installs use InnoDB and on most shared hosts you don't have a choice anyway. Info about on the MySQL documentation: Or less technically the obvious wikipedia: |