Global indexing view
-
Yurii Rashkovskii
- Assigned user set to Yurii Rashkovskii
-
Oleg Andreev
- State changed from new to open
- Assigned user changed from Yurii Rashkovskii to Oleg Andreev
-
Yurii Rashkovskii
do you want me to takeover this ticket?
-
Oleg Andreev
Raw ideas:
0) Semantics are the same, MySQL has: try the longest keys prefix to use an index, then filter the data with a brute force.
1) DSL: index_slots :a, :b, [:x, :y]
2) find(:a => 1) uses the index upon :a, find(:x=>) or find(:x=>, :y=>) uses the index upon both slots :x and :y.
3) Don't try to put hash values into the key: there's absolutely no sense in searching by the hash value (also, ordering issues arise).
In-depth search (kinda xpath or inverted index species) can be implemented in a different configurable views.
-
Yurii Rashkovskii
just as a crazy idea: will it make any sense to define some slots indexable when they're queried first time?
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.