Task #5223
open
migrate sinedon to be compatible with InnoDB sql engine
Added by Anchi Cheng about 7 years ago.
Updated over 6 years ago.
Description
This will open up the possibility of several features that helps database management.
- Related to Task #5318: avoid calling MySQLdb directly to connect when sinedon.cfg is read as input kwargs added
The default is still MyISAM. To switch to create new tables in InnoDB, you need to
- change /etc/my.cnf default_storage_engine to InnoDB
- restart mysql service
- modify your working sinedon.cfg to include at global level
engine: InnoDB
Anchi, have we done anything to address the FOREIGN_KEY aspect of InnoDB
CREATE TABLE Orders (
OrderID int NOT NULL,
OrderNumber int NOT NULL,
PersonID int,
PRIMARY KEY (OrderID),
FOREIGN KEY (PersonID) REFERENCES Persons(PersonID)
);
ALTER TABLE AcquisitionImageData
ADD FOREIGN KEY (`REF|SessionData|session`) REFERENCES SessionData(DEF_id);
I am trying to learn the ins and outs of InnoDB vs. MyISAM and what I can tell it looks we'll need to connect the tables using the FOREIGN KEY flag, especially if we want the multi-master setup to work. Otherwise, it wouldn't know how to properly connect the tables together when locking rows.
- Related to Feature #5951: Create a MariaDB Galera multi-master Cluster using Docker added
No, I have not looked at Foreign Key, yet.
Also available in: Atom
PDF