The query we used is "SELECT * FROM Brand ORDER BY BrandDescription". The Brand table contains more than 30,000 records. The execution time is reasonable when we execute in the system.But it is slower when we execute the same in the device.
Regards, Farzana. Igor Tandetnik wrote: > > "Farzana" <[EMAIL PROTECTED]> > wrote in message news:[EMAIL PROTECTED] >> We have already created such index but we have to use ORDER BY in the >> query explicitly to sort the data by BrandDescription. > > Of course. Why do you believe this is a problem? How else do you expect > SQLite to know you want results sorted by this column? SQLite will see > there's a suitable index, and will use it to speed up ORDER BY clause. > > If the query is still slower than you hoped, post the statement here, > and also post the output of this statement: > > explain query plan select <the rest of your statement here>; > > Igor Tandetnik > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > -- View this message in context: http://www.nabble.com/nVARCHAR-as-unique-index-tp17206197p17229808.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
