Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 4 of 4 total |
CaseInSensetive index = UN-OPTIMIZED queries ? |
Wed, Dec 20 2006 4:59 AM | Permanent Link |
Max Terentiev | Hello,
I have very simple test table: ID:AutoInc Name:String[30] I also create non-unique case IN-Sensetive index for Name field. Why simple queries like: SELECT * FROM TestTable WHERE Name='smith' SELECT * FROM TestTable WHERE Name LIKE 'jhon%' Is always UN-OPTIMIZED ?? This queries becomes OPTIMIZED only after altering table and removing case IN-Sensetive option from Index. I should avoid using case insensetive indexes ? What is faster: 1. case sensetive indexes and queries like SELECT * FROM TestTable WHERE LOWER(Name)='smith' 2. case INsensetive indexes and queries like SELECT * FROM TestTable WHERE Name='Smith' Thanx for help ! |
Wed, Dec 20 2006 7:14 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Max
I think you need to do SELECT * FROM TestTable WHERE LOWER(Name)= LOWER('smith') which lets the engine know what's going on Roy Lambert |
Wed, Dec 20 2006 7:55 AM | Permanent Link |
"Jose Eduardo Helminsky" | Max
When you use case-insensitive indexes you must follow a simple rule, use UPPER or LOWER to really use the index otherwise it will be un-optimized. Eduardo |
Wed, Dec 20 2006 8:52 AM | Permanent Link |
Max Terentiev | LOWER() function helps !
Thank you very much ! |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |