Re: How should I make text column search faster?
Rick, you are always very helpful.
As there will no search for parts of the address like Street, City etc so exact matching of hash is fine. And i know there will be no range scans and its not needed too (though its not possible with hashes too).
One more clarification about search type is that it would be exact match.
>>Since either the hash or the direct index will be too big to be cached, why not >>keep it simple and not do the hash.
Well, hash would take only 16 bytes in binary(16) but index on address column would take 70bytes so don't you think its a good difference worthy to bear the overhead of calculating hashes?
Currently its MyISAM and I intend to keep it because though there are lot of benefits of InnoDB but as it uses clustered index so it will be heavy on RAM.
After index is built on hash column.. do you think there will still be need for declaring unique constrain on address column? If suppose address column is declared unique then there will be two indexes in total? And all the benefits of doing hashes will be gone?
Subject
Written By
Posted
September 14, 2011 01:06PM
September 15, 2011 09:17AM
Re: How should I make text column search faster?
September 15, 2011 11:22AM
September 16, 2011 07:42PM
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.