We are looking at porting the index code in the index package(and YES keeping the licensing along with it) but modifying that index code to be able to use a backing store of a nosql database. I like this code better than lucene's since it is not polluted with text search stuff.
Now, I have never written index code nor taken a database class(was an electrical engineer, but do understand b-trees), sooooo, one question I have is the index structure. If I index 5 columns A, B, C, D in one table, is there one index tree for that table or four index trees for that able. Every time I look at lucene or H2, it seems to be one index tree, but that woudn't make sense if I were to query on column D being some value, as the tree can only be sorted by A, B, C, D with one of the columns being first. I guess I am looking for a little bit of a push before I dive into this port. Any good books to read on this subject as well or links on the web would be great!!!!!! thanks, Dean -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/2-_BEh6CmiEJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
