On Thu, Jun 20, 2013 at 10:43 AM, Tom Holden <[email protected]> wrote:
> > Richard, I think I know why your test of the command line shell returned > no error – an index is needed on the field with the missing collation. I am > guessing what has changed is that the query optimiser now (unnecessarily?) > selects an appropriate index, if one exists, even for a simple SELECT with > no ordering or other function desirous of an index. > The use of an index rather than the original table when doing a scan is a feature, not a bug. You can work around it by adding "ORDER BY rowid" to your query. -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
