support

Author Topic: InnoDB support  (Read 25120 times)

Offline abantecart

  • Administrator
  • Hero Member
  • *****
  • Posts: 4358
  • Karma: +299/-10
    • View Profile
    • Ideal Open Source Ecommerce Solution
InnoDB support
« on: October 07, 2016, 02:18:30 PM »
We got few inquiries for conversion/migration to Innodb database engine for MySQL or MarinaDB

There is a lot of discusstions with pros/cons about InnoDB vs MyISAM.
Even three are some benefits of using InnoDB, some disadvantages are there and fine tuning is required for InnoDB.

Because of these, we cannot make InnoDB as default database engine for AbanteCart. This can have a negative effect on initial installation of AbanteCart if people have hosting limitations.

However, for advanced users, we can include an option with InnoDB installation or migration.

This is where we need user's help us and fund this project.

Please PM if you are interested, and feel free to discuss more in this post
Please  rate your experience or leave your review
We need your help to build better free open source ecommerce platform for everyone. See how you can help

Offline OneMore

  • Newbie
  • *
  • Posts: 46
  • Karma: +12/-0
    • View Profile
Re: InnoDB support
« Reply #1 on: December 09, 2023, 03:04:11 PM »
Although InnoDB has some benefits over MyISAM, at least on the paper, I have completely come back from using it after a database corruption, at least for all my mutiple website developements on localhost.

With MyISAM, when you want to backup the database of a site, you simply copy the mysql/data/<your-website> folder in which are the .MYD, .MYD, .frm files. The copy-paste method works for restoring databases.

With InnoDB, the databases of your miscellaneous websites are all linked together into a very few files.
In some cases of database corruption, file copy-paste operations usually don't work and will even corrupt your database.
You can play during whole days, weeks or more trying to solve database errors and restoring your database, and be unsuccessful at the end. This arrived to me few years ago. Never more.
For experts, I think it is possible to configure InnoDB differently, for the average user, it has a complexity of which he is unaware.

Of course, InnoDB is likely more stable than few years ago and database recovery tools may have improved as well.
(They were really few available when the crash occured for me.)
Of course it is also still possible to export SQL dumps to backup databases.
An InnoDB expert would also probably know what to do when the database crashes.

But as for myself, although InnoDB is in use on some webhosts, I strongly prefer staying with MyISAM for my local projects.

 

 

Powered by SMFPacks Social Login Mod