FrontAccounting forum — Why ENGINE=MyISAM + ENGINE=InnoDB

Re: Why ENGINE=MyISAM + ENGINE=InnoDB

null@example.com (apmuthu) — Thu, 12 Sep 2013 14:15:11 +0000

Making all as ENGINE=InnoDB is okay as far as FA v2.3.x is concerned - it just won't use the Foreign Key CASCADE ON INSERT/DELETE/UPDATE feature..

Re: Why ENGINE=MyISAM + ENGINE=InnoDB

null@example.com (scanreg) — Tue, 10 Sep 2013 13:01:58 +0000

I believe InnoDB supports "transactions", not money, but a type of db action that does not commit unless the full action is completed

Re: Why ENGINE=MyISAM + ENGINE=InnoDB

null@example.com (swheeler) — Mon, 09 Sep 2013 18:56:19 +0000

change to InnoDB if you need to perform transactions. Itronics has indicated that change to this storage method has no negative implications.

Why ENGINE=MyISAM + ENGINE=InnoDB

null@example.com (wildone) — Mon, 09 Sep 2013 18:32:11 +0000

In the setup of the DB tables I see that 2 different engines are installed.
Why ENGINE=MyISAM + ENGINE=InnoDB instead of only 1 of the 2?

Does someone knows this and can explain it to me.