Andrew Tridgell 73c8566d95 use the unique flag on ldb attributes to optimise & clauses ... When a attribute is marked unique we know that if we find a match it will be the only possible match. This means that in a list of subtrees connected by an &, it is best to first load the index values for the unique entries, as if they find something then we know we won't have to look any further. This helps with searches like this: (&(objectclass=user)(samaccountname=tridge)) the old code would first have loaded the very large index for the objectclass=user attribute, and then loaded the single entry for samaccountname=tridge. Now we load the samaccountname=tridge entry first, notice that it gives us a single result, and stop, thereby skipping the load of the objectclass=user index record completely.		2009-06-01 22:03:20 +10:00
..
ldb_cache.c	don't load @ATTRIBUTES if we have an override handler in place	2009-04-07 16:34:18 +10:00
ldb_index.c	use the unique flag on ldb attributes to optimise & clauses	2009-06-01 22:03:20 +10:00
ldb_pack.c	Fix the mess with ldb includes.	2009-01-30 01:02:03 -05:00
ldb_search.c	a useful debugging tool	2009-05-28 16:11:45 +10:00
ldb_tdb_wrap.c	Fix the mess with ldb includes.	2009-01-30 01:02:03 -05:00
ldb_tdb.c	added support for a prepare_commit() op in ldb modules	2009-03-31 15:07:54 +11:00
ldb_tdb.h	added support for a prepare_commit() op in ldb modules	2009-03-31 15:07:54 +11:00