CiviCRM Community Forums (archive)

My webhost returned this email to me when I asked to enable the INNODB.

INNODB is a table type, not a database-wide setting.
If your CMS requires INNODB format, when it creates the database tables it should automatically set them to the appropriate type.

--------------------------

I think the webhost will doit for me, but it appears I gotta provide the how to.

Drupal is web application I plan to use with CIVICRM

Any links or suggestions will be appreciated

My webhost mentioned this


INNODB is enabled in MySQL unless it is specifically restricted, and we have not restricted it, so you can use it.

All you need to do to create INNODB tables is include TYPE=INNODB in the table create statement.

My CMS installations create their own table structure, so I would think that if CIVICRM requires INNODB, the routines which create the tables will create them with TYPE=INNODB

Install 1

OK I do a standard Drupal install, which is MYISAM.

Then I create a MYSql db per the "green instructions above" for the CIVICRM...then install the CIVICRM is that a proper install procedure.

Install 2

OR DO I create a MySql db per the "green instructions above" for Drupal, then install the drupal

then created a MySql db per the "green instructions above" for Civicrm, the install the Civicrm


I prefer not to have problems with the database in either application, and I'd like to avoid problems once the site is working.

It would seem the INNODB would be the way to go on both, but I haven't read enough to know the best method so far.

Any links or help would be appreciated.

Thanks






How does the above sound to you?

The site will not require alot of data in the Drupal db.

THe civicrm db will be large constantly updating as new members join site.

The Drupal security releases are so frequent I don't want to have difficulty to update.

As you mentioned a separate db for each was my intent.

I just didn't know how friendly drupal would be with the INNODB over time.

Did a little searching the drupal site about the INNODB and there isn't much mentioned.

One of concerns is the modules for drupal.  There are constantly issues being repaired etc with modules.

I'm not sure modules alone wouldn't be enough reason to stay with MyISAM for the Drupal part of the site.

If it is just a matter of what I choose to do I can accept that, but if there is a best way.

That is what I want to do.

------------------

I do have three more sites currently live production drupal sites, which I would like to apply the CIVICRM to as well.

So, alterning those db could be more complex or less.   I'm thinking it sure would be good, if I could just create a new INNODB for each of those sites and install the CIVICRM.

First, I've gotta get this site up and spend a couple weeks working with it before I think about he additional sites.

Thank you for your responses.