Commit a8670f40 authored by Jérome Perrin's avatar Jérome Perrin

full_text_mroonga_catalog: don't use VARBINARY columns in index

Mroonga 14.07 seems to have a problem that such columns can not be
selected, but VARCHAR seems OK.

See discussions on slapos!1644
parent 2e49e7e1
CREATE TABLE `content_translation` ( CREATE TABLE `content_translation` (
`uid` BIGINT UNSIGNED NOT NULL, `uid` BIGINT UNSIGNED NOT NULL,
`property_name` VARBINARY(100), `property_name` VARCHAR(100) BINARY,
`content_language` VARBINARY(100), `content_language` VARCHAR(100) BINARY,
`translated_text` TEXT, `translated_text` TEXT,
PRIMARY KEY (`uid`, `property_name`, `content_language`), PRIMARY KEY (`uid`, `property_name`, `content_language`),
FULLTEXT KEY (`translated_text`) COMMENT 'parser "TokenBigramSplitSymbolAlphaDigit"' FULLTEXT KEY (`translated_text`) COMMENT 'parser "TokenBigramSplitSymbolAlphaDigit"'
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment