Install with MySQL NDBCLUSTER storage engine

[yxiao]

I would like to have this feature in the installation - The user is given an option to use MySQL cluster engine
NDBCLUSTER instead of using default MyISAM engine. It would greatly increase the reliability of the whole system.

Users could also convert MyISAM database to NDBCLUSTER database later. But I am not sure what
would happen if the user creates new modules with Module Builder.

[stesin]

Seems that nobody really knows (and/or cares) about this kind of setup? I already asked the same question in the "help" forum, in a hope that somebody will drop a word or two...

[joey]

As far as choosing your table type, Sugar will automatically default to your default storage engine, which is MyISAM on all default MySQL server installs currently.

If you'd like for all tables to be created as type NDB (NDBCluster), add this to your my.cnf file prior to running the Sugar installation:

default-storage-engine=NDB

As far as running NDBCluster in general and its compatibility with Sugar, since we're not explicitly defining any constraints around foreign keys and aren't doing any cascading updates and deletes, the NDB engine should just work.

Let me know if you have information to the contrary!

Thanks,
Joey Parsons