On 5 Feb 2014, at 18:40, Dan Kennedy 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
On 02/06/2014 01:22 AM, Kevin Martin wrote:
Hi,
My questions are basically:
1) What causes sqlite3 to call xRowid
2) If I don't want to update my virtual table, or do a select ROWID, can I just
use an incremental counter, increased on every call to xNext (bearing in mind
the order of my data
Hi,
My questions are basically:
1) What causes sqlite3 to call xRowid
2) If I don't want to update my virtual table, or do a select ROWID, can I just
use an incremental counter, increased on every call to xNext (bearing in mind
the order of my data is not guaranteed, so this won't necessarily r
>> 2. In case the virtual table implementation needs to allocate memory in
>> order to uniquely
>> describe a row/item, this memory needs to be freed when no longer used. As I
>> see it, there is no
>> such method in the Virtual Table implementation.
>
>Maybe the transaction part of the virtual
> I have played with the new Virtual Table interface from CVS and found some
> shortcommings for the
> current implementation of the xRowID method:
>
> int (*xRowid)(sqlite3_vtab_cursor*, sqlite_int64 *pRowid);
>
> As far as I understand, this function is called by SQLite whenever it needs a
Hello All,
I have played with the new Virtual Table interface from CVS and found some
shortcommings for the current implementation of the xRowID method:
int (*xRowid)(sqlite3_vtab_cursor*, sqlite_int64 *pRowid);
As far as I understand, this function is called by SQLite whenever it needs a
un
6 matches
Mail list logo