DB Tuner changed the collation of all the tables in the database and not only the tables concerned by the site where I configured DB Tuner. I have several sites in one database, each one has a prefix for their tables.

Comments

mikeytown2’s picture

mikeytown2 commented

It changes all tables in that database. There isn't a good way to only select the tables that pertain to that database. It operates by doing a SHOW TABLES db query. I'm not sure what the best way to handle this is...

What does your prefix in your settings.php look like?

dalin’s picture

dalin
he/him
Primary language English
Location 🇨🇦, 🇲🇽, 🌍
commented

Could you get the data with schema API?

mikeytown2’s picture

mikeytown2 commented

even though no one uses it; it appears that you can get the entire schema of that drupal install via
drupal_get_schema.

Open up some better possibilities in terms of detecting other drupal installs on the database and tables not in use. I see there's a drupal_alter('schema', $schema); in there... that opens up some possibilities via hook_schema_alter; well it will at least make the database keys added by dbtuner and the schema match. Means I would feel comfortable with a features export of keys added to CCK fields then.

rondev’s picture

rondev commented

What does your prefix in your settings.php look like?

d6x_
d7n_
...

rondev’s picture

rondev commented

The project DB maintenance doesn't have the prefix taken in account too.
But in that module you can choose the tables you want to optimize.

mikeytown2’s picture

mikeytown2 commented

I'm not a big fan of DB maintenance because I have to add tables every time I add a module. I think schema is the correct way to do this.