mongodb compound index over extending -

-

i have question regarding compound indexes cant seem find, or maybe have misunderstood.

lets have created compound index {a:1, b:1, c:1}. should make according http://docs.mongodb.org/manual/core/indexes/#compound-indexes

the following queries fast.

db.test.find({a:"a", b:"b",c:"c"}) db.test.find({a:"a", b:"b"}) db.test.find({a:"a"})

as understand order of query important, explicit subset of {a:"a", b:"b",c:"c"} order important?

lets query

db.test.find({d:"d",e:"e",a:"a", b:"b",c:"c"})

or

db.test.find({a:"a", b:"b",c:"c",d:"d",e:"e"})

will these render useless specific compound index?

compound indexes in mongodb work on prefix mechanism whereby a , {a,b} considered prefixes, order, of compound index, however, order of fields in query not matter.

so lets take examples:

db.test.find({d:"d",e:"e",a:"a", b:"b",c:"c"})

will use index:

db.ghghg.find({d:1,e:1,a:1,c:1,b:1}).explain() {         "cursor" : "btreecursor a_1_b_1_c_1",         "ismultikey" : false,         "n" : 1,         "nscannedobjects" : 1,         "nscanned" : 1,         "nscannedobjectsallplans" : 2,         "nscannedallplans" : 2,         "scanandorder" : false,         "indexonly" : false,         "nyields" : 0,         "nchunkskips" : 0,         "millis" : 0,         "indexbounds" : {                 "a" : [                         [                                 1,                                 1                         ]                 ],                 "b" : [                         [                                 1,                                 1                         ]                 ],                 "c" : [                         [                                 1,                                 1                         ]                 ]         },         "server" : "ubuntu:27017" }

since a , b there.

db.test.find({a:"a", b:"b",c:"c",d:"d",e:"e"})

depends upon selectivity , cardinality of d , e. use compound index whether use in such manner allows decent performance of query depends heavily upon what's in there.


Popular posts from this blog

Php - Delimiter must not be alphanumeric or backslash -

-
this question has answer here: delimiter must not alphanumeric or backslash , preg_match 5 answers this question has been asked don't know how fix problem in situation. getting following php errror: php message: php warning: preg_match(): delimiter must not alphanumeric or backslash in... on line 227 line 227 following: if (preg_match($match, $_server['http_user_agent'])) and function: $oslist = array ( 'windows 3.11' => 'win16', 'windows 95' => '(windows 95)|(win95)|(windows_95)', 'windows 98' => '(windows 98)|(win98)', 'windows 2000' => '(windows nt 5.0)|(windows 2000)', 'windows xp' => '(windows nt 5.1)|(windows xp)', 'windows server 2003' => '(windows nt 5.2)', 'windows vista' => '(windows nt 6.0)', 'w...
Read more

Delphi interface implements -

-
i expect reference counting should work on outer aggregating object in interface implementation. if can refer example: clarity in classes implementing multiple interfaces (alternative delegation): here minimal reproduction of behaviour: program so16210993; {$apptype console} type ifoo = interface procedure foo; end; tfooimpl = class(tinterfacedobject, ifoo) procedure foo; end; tcontainer = class(tinterfacedobject, ifoo) private ffoo: ifoo; public constructor create; destructor destroy; override; property foo: ifoo read ffoo implements ifoo; end; procedure tfooimpl.foo; begin writeln('tfooimpl.foo called'); end; constructor tcontainer.create; begin inherited; ffoo := tfooimpl.create; end; destructor tcontainer.destroy; begin writeln('tcontainer.destroy called');//this line never runs inherited; end; procedure main; var foo : ifoo; begin foo := tcontainer.create; foo.foo; end; begin main; readln...
Read more

trac - Modifying workflow to add a status and split on ticket type -

-
i hoping can me lost. need modify workflow trac if ticket type spr, gets assigned our qa, , ones allowed closing ticket. otherwise, goes test team closed. as well, need ticket status flow follows: new ticket(bug) -> assigned(dev) -> fixed(re-assigned test or spr) -> closed/re-opened currently appears ticket set closed after dev fixes issue. i not familliar trac @ , have been hammering away @ 2 days , can't seem work. incredibly appreciated! try advancedticketworkflowplugin , because able act differently based on ticket field values. relevant here: triage operation based on ticket type according wiki documentation: accept = new -> * accept.name = accept ticket workflow accept.operations = triage accept.triage_field = type accept.triage_split = defect->new_defect,enhancement->new_enhancement (see more complete example on wiki page linked above)
Read more