![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 4 of 4 total |
![]() |
Wed, Aug 10 2022 1:46 PM | Permanent Link |
Ian Branch | Hi Team,
Given varchar fields with 2 or 3 characters in them, what are the pros & cons of Indexing them v Text Indexing them?? Regards & TIA, Ian |
Wed, Aug 10 2022 3:55 PM | Permanent Link |
Raul ![]() | On 8/10/2022 1:46 PM, Ian Branch wrote:
> Given varchar fields with 2 or 3 characters in them, what are the pros & cons of Indexing them v Text Indexing them?? No expert on text indexes so take this with a grain of salt but normal indexing is way to go IMHO. You're basically working with a single string value in this case. Text indexing was designed to find word(s) in a column and in your case you have a "single word" only. Note that EDB by default does not add anything with less than 3 letters into text index so your 2 char entries would not be part of text index anyways. Raul |
Thu, Aug 11 2022 2:19 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Ian
I'll support Raul use normal indexing - text index for other than a "collection" of words is a waste of time. Normally it will be a CLOB but could be a varchar with multiple pieces if inofrmation (eg a short product description) Roy Lambert |
Thu, Aug 11 2022 2:23 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Ian
Thinking about it a bit more wether its even worth indexing at all will depend on the data, how much variability there is, sometimes a row scan can be as fast and you don't have the bother of maintaining an index. You need to carry out a few tests to see. Roy Lambert |
This web page was last updated on Monday, July 14, 2025 at 02:20 AM | Privacy Policy![]() © 2025 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |