>> 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
3 matches
Mail list logo
