>>The standard way to have non-TEXT information associated with rows in
>>an fts table would be a separate table which joins with the fts table
>>on rowid.
>
>I have not tested this, but if the FTS2 rowid is the standard SQLite rowid, I
>believe that it will be affected by VACUUM change of rowids recently reported
>on this list? If so, could this be fixed?
VACUUM does modify FTS2 rowids. Here is the test:
drop table if exists a;
create virtual table a using fts2 (t);
insert into a (t) values ('one');
insert into a (t) values ('two');
insert into a (t) values ('three');
select rowid, * from a;
delete from a where t = 'two';
vacuum;
select rowid, * from a;
Unfortunately there is no workaround since table a is auto-generated by the
FTS2 module. Created ticket #2510.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
