> This is true even if rowid is aliased by an INTEGER PRIMARY KEY.

Thanks. Just to be clear, I think this is the scenario when you don’t set your primary key but other columns in your insert statement.

CREATE TABLE t(x INTEGER PRIMARY KEY, y);

INSERT INTO(y) VALUES(‘value’);

Otherwise, if you set primary key in your insert statements, you’ll be fine I guess.

I’m not worried about reusing ids but if ids change e.g on vacuum, it is a disaster. Because people use row id(via last_insert_row_id()) assuming it won’t change but vacuum changes it and now you have a “dangling id”, if you fetch data again with that id, either you won’t find the row or get some other random row.