Re: Iterating through SQL table

[K R]

"For this table to be queryable, `docIDs` needs to be projected to a child table in which each row has its matching `hashvalue` from this table ,and that individual docID. Then your query becomes trivially easy, and so does processing it. "

Sorry, I don't quite get it, what you mean. One DocID has many hashvalues, so it cannot be used as primary key. Do you mean

1. DocID (int) | hashvalue (int)

or

2. DocIDs (text) | hashvalue (int, Primary key)


or what?

In the second case I'll have two tables (hashvalue, count) and (docIDs, hashvalue)and I'll have to JOIN for all the queries, would it really work faster?

Thanks



Edited 3 time(s). Last edit at 04/28/2009 12:10AM by K R.