This issue is part of several I am opening in order to add support for ndbcluster to Drupal core. Core can fail when creating or importing the locale_sources table into an ndbcluster database.

Use case: Jack wants to use ndbcluster engine table type to manage Drupal as opposed to MyISAM.
Scenario: Jack tries to install Drupal but the database fails to be created failing with error:
BLOB column 'source' "can't be used in key specification with the used table type"

Fix: Change source from BLOB to varbinary or varchar data type, or remove the KEY specification.

Not sure what size varbinary or varchar we would need. ndbcluster limits us to 32kb / row specification so have to keep that in mind when considering how much data to put in.

Potential issues: Limiting row size would probably be more problematic than the performance loss from removing Key so I would suggest that solution. I don't know how to test the performance implications of that very well, but I will try when I get time using devel module.

Comments

jhedstrom’s picture

Issue summary: View changes
Status: Active » Closed (duplicate)

I think this is now works as designed since the encoding changes that went in with #1314214: MySQL driver does not support full UTF-8 (emojis, asian symbols, mathematical symbols).