Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Binaries » View Thread |
Messages 1 to 3 of 3 total |
Example of problem with index Case-Sensitive |
Fri, Jul 25 2008 1:41 PM | Permanent Link |
Francisco Fernandez | Tim, Roy
After many tests i could have verified that the problem with performance with index Case-Sensitive comes when i have triggers in the table that update another tables. I have prepared an example for you where you can see it easily. In the code there are two buttons where update four records of a table, one button with index Case-Sensitive and one button with index Case-Insensitive. You can see that with the same code the manage with index Case-Sensitive is more slowly than Case-Insensitive. The project must be at a folder called C:\Example to run. Thank you very much Attachments: Example.rar |
Fri, Jul 25 2008 2:10 PM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Francisco
Since the collation for the index and the collation for the column are different you need to give ElevateDB a hint that it should be looking at a case sensitive index..... PREPARE stmt FROM 'SELECT * FROM Articulos WHERE CODIGO COLLATE ANSI =? Roy Lambert |
Sat, Jul 26 2008 4:37 AM | Permanent Link |
Francisco Fernandez | Roy
Great, i didn't know that was especify collation in trigger. Thank you very much for all. |
This web page was last updated on Friday, March 29, 2024 at 03:30 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |