indexing - mysql fulltext index is used for MATCH() AGAINST but not for = -

-

my table xm_c created this: 

 create table `xm_c` (     `category_id` char(16) not null default '',     `label` char(64) not null default '',     `flags` smallint(5) unsigned default null,     `d0` date default null,     `d1` date default null,     `ct` int(6) unsigned default null,     `t_update` timestamp not null default current_timestamp on update current_timestamp,      primary key  (`category_id`),     **fulltext key `label` (`label`)**   ) engine=myisam default charset=latin1 delay_key_write=1;

the fulltext index not used in query below:
select * xm_c label = 'tomcruise';

where used here:
select * xm_c match(label) against('tomcruise');

 mysql> explain select * xm_c match(label) against('tomcruise');    >   id | select_type | table | type | possible_keys | key  | key_len | ref  | rows |    **1 | simple      | xm_c  | fulltext | label     | label | 0      |      |    1 | using where**      mysql> explain select * xm_c label = 'tomcruise';    > id | select_type | table | type | possible_keys | key  | key_len | ref  | rows    |   **1 | simple      | xm_c  |  | label         | null | null    | null | 5673360 | using where**

can explain this? shouldn't index used in both queries?
there syntax constraint in using fulltext indices?

a full text index can used in match() ... against operations. = operator different , has nothing fts, can't use type of index. more information fts can found in manual.

a horse uses horseshoes, car uses tyres. , both can bring b.


Comments

Post a Comment

Popular posts from this blog

Javascript line number mapping -

-
magically formatted comments change reported line number of javascript errors in browsers; this: //@line n "f" n line number , f file name. unfortunately, //@line appears ungoogleable. know there documentation on feature, , browsers support it? (i found references here , here .) from can find available in mozilla based browsers. it using js_setoptions command can turn these options on or off depending on values passed. https://developer.mozilla.org/en/js_setoptions
Read more

c# - Is it possible to remove an existing registration from Autofac container builder? -

-
something along lines: builder.registertype<mytype>().as<itype>(); builder.registertype<mytype2>().as<itype>(); builder.deregistertype<mytype>().as<itype>() var container = builder.build(); var types = container.resolve<ienumerable<itype>>(); assert.istrue(types.count == 1); assert.istrue(types[0].gettype == typeof(mytype2)); scenario: go through bunch of assemblies , go register types want make sure have 1 implementation of given type. need before create container. track on own nice if autofac me bit. this cannot done directly using containerbuilder , unless start on new one. mind you, having first built container should able construct new container filtering away unwanted types , reusing registrations first container. this: ... var container = builder.build(); builder = new containerbuilder(); var components = container.componentregistry.registrations .where(cr => cr.activator.limittype != typ...
Read more

php - Mysql PK and FK char(36) vs int(10) -

-
i have read mysql can handle indexes , searches better if tables keys integers rather char(36) uuid's. is worth converting int(10)? note: use 1 server , have have plans use multiple databases concurrently therefore removing 1 of big reasons using uuid. our tables innodb if makes difference. thanks in advance. usually rdbms can handle integer keys pk more efficient, other datatypes. reason how build index column, yes: long dont require string (or other typed) keys, should use integers. however: char(36) , int(10) far away being equal, because int(10) much smaller, char(36). dont know, if require many different keys, should keep in mind. update, complete last paragraph: int(10) 32-bit, char(36) 36 - ^byte^ (= 288-bit). not mean, int consumes less space, means, char(36) has 4 times more different keys.
Read more