Another possibility: I noticed on <https://www.sqlite.org/rowidtable.html> this note: > If the rowid is not aliased by INTEGER PRIMARY KEY then it is not persistent and might change. In particular the VACUUM command will change rowids for tables that do not declare an INTEGER PRIMARY KEY. Therefore, applications should not normally access the rowid directly, but instead use an INTEGER PRIMARY KEY. I ran `VACUUM` on that database quite often. Is it possible that running `VACUUM` is rewriting the `rowid` values for the `licenses` table but leaving the values in the `licenses_fts` table unchanged? If so, maybe I get a new set of orphaned duplicate rows every time I vacuum?