MySQL Forums
Forum List  »  Full-Text Search

ERROR 1253 (42000): COLLATION 'utf8_bin' is not valid for CHARACTER SET 'binary'
Posted by: Fco. Mario Barcala Rodríguez
Date: October 31, 2008 06:22AM

I don't know why I get this error when doing:

select token from token where MATCH(token) AGAINST ('monogramatico' IN BOOLEAN MODE) COLLATE utf8_bin;

Here are additional info:

mysql> show create table token;

| token | CREATE TABLE `token` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`token` varchar(150) DEFAULT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `token_textlike` (`token`),
FULLTEXT KEY `token_text` (`token`)
) ENGINE=MyISAM AUTO_INCREMENT=146903 DEFAULT CHARSET=utf8 |


mysql> show variables like 'CHARACTER%';
+--------------------------+----------------------------------------+
| Variable_name | Value |
+--------------------------+----------------------------------------+
| character_set_client | utf8 |
| character_set_connection | utf8 |
| character_set_database | utf8 |
| character_set_filesystem | binary |
| character_set_results | utf8 |
| character_set_server | utf8 |
| character_set_system | utf8 |
| character_sets_dir | /usr/local/mysql/share/mysql/charsets/ |
+--------------------------+---

mysql> select version();
+---------------+
| version() |
+---------------+
| 5.1.26-rc-log |
+---------------+


Perhaps a bug of this version?

Mario Barcala

Options: ReplyQuote


Subject
Views
Written By
Posted
ERROR 1253 (42000): COLLATION 'utf8_bin' is not valid for CHARACTER SET 'binary'
10249
October 31, 2008 06:22AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.