> I am not understanding why having a hash and the full url in the > database would not take care of the collisions. Even if you had > 10 collisions for a 16 bit hash (say), if your query was: > SELECT ... WHERE hash=thehashvalue AND url='theurl' you would get > very fast lookups on the hash and the url comparison would not > add much to the query at that point. You could even do a partial > index on the url, e.g. "KEY( hash, url(200))". > > b. >
That would work, but it was my understanding that they want the key itself to take care of uniqueness. If not, then you can do it that way. However, I would not include part of the URL in the index -- see my previous message about the key buffer. Steve Meyers --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php