On 5 Feb 2014, at 18:40, Dan Kennedy <danielk1...@gmail.com> wrote: > But is it the case that your virtual table doesn't handle > anything other than full scans of the entire table contents? If > so, it's probably not a problem if rowids are inconsistent.
Thanks for the heads up on the 'or' case, I didn't know that. I don't use xBestIndex, so the table only supports full scans. I think I'll try it with returning SQLITE_ERROR in xRowid, because I'd rather see the error than have strange results happen silently, I'll, watch what happens. One of the columns in the underlying table/view is unique, so one solution is to order by that column when doing the internal select, and then the auto generated row ids will be consistent, but that just feels like it adds a lot of calculation I don't want to do, and won't be necessary most of the time. Thanks, Kevin _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
