Re: word index - is there a better solution?
taking your advise from an earlier post, I came to realize that I just need a single primary key (no idea why I didn't see that myself) because all queries on this table are first gonna look for lang and word_location and then select the word_id from what's left.
word_id will never be selected outside the context of lang/word_location, doc_id will always be the result.
I'm currently thinking of splitting up the table into smaller ones along the lines of
words_in_docs_en_location1
words_in_docs_en_location2
words_in_docs_en_location3
words_in_docs_de_location1
etc.
this would also allow me to eliminate the columns lang and word_location. On the downside, I would have like 60 word location tables sitting in my DB.
I've already seen servers with 512G RAM, however, so 1T is not too far away and it may be worth looking into that because 1T may just be enough to fit any one of the lang/location tables into.
Finally, I removed the phrase search (the second table) from the concept for now. I did some research on phrase search and this is not as trivial as I thought (in fact, I probably have a simple solution, but it's most likely useless for anything that has more than a few thousand rows).
Subject
Views
Written By
Posted
4748
June 03, 2010 01:36PM
1583
June 04, 2010 07:40PM
1502
June 04, 2010 08:49PM
1573
June 04, 2010 11:33PM
1381
June 05, 2010 12:21AM
1409
June 05, 2010 12:41PM
1581
June 05, 2010 01:45PM
1429
June 05, 2010 09:13PM
1239
June 06, 2010 10:13AM
1438
June 06, 2010 07:36PM
1394
June 06, 2010 08:29PM
1385
June 07, 2010 09:29AM
Re: word index - is there a better solution?
1332
June 07, 2010 01:02PM
1062
August 27, 2010 08:37PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.