On 1 Apr 2010, at 2:55am, Rashed Iqbal wrote: > Thank you, all for your responses. I did not have access to table > definition so I used collate no-case within statements. However, I still > have very slow performance of the DB.
If you are using a different collation to the one the column is defined with, any index based on that column cannot be used. Because an index with one collation is not the same as an index on the same columns but with a different collation. So the slowdown you are seeing is because your SELECT query can no longer use any indexes: SQL has to go through every record in the table every time you execute a query. If you absolutely cannot change the table definition, you need to be able to create indexes with your preferred collation. Or perhaps you can simulate one or the other using a VIEW. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
