[sqlite] Are columns declared as 'INTEGER PRIMARY KEY' guaranteed not to change except from UPDATE statements?

Thanks a lot both Igor and Simon for the quick response! Your two answers settle my doubts. On Mon, Nov 16, 2015 at 3:48 PM, Simon Slavin wrote: > On 16 Nov 2015, at 12:24am, Randy Eels wrote: > > > My main question is: is an 'INTEGER PRIMARY KEY' column guaranteed not to > > change, except as

[sqlite] Are columns declared as 'INTEGER PRIMARY KEY' guaranteed not to change except from UPDATE statements?

> Any column declared as 'INTEGER PRIMARY KEY' is said to be an alias for > the internal 'rowid' column, and this > really-need-to-know/> > proves > that 'rowid' can change after a 'vacuum' statement is issued. Merely >

[sqlite] Are columns declared as 'INTEGER PRIMARY KEY' guaranteed not to change except from UPDATE statements?

On 16 Nov 2015, at 12:24am, Randy Eels wrote: > My main question is: is an 'INTEGER PRIMARY KEY' column guaranteed not to > change, except as a consequence of ordinary UPDATE statements? (And in > particular, not as a consequence of a 'vacuum' statement.) Values in the rowid column (which has a

[sqlite] Are columns declared as 'INTEGER PRIMARY KEY' guaranteed not to change except from UPDATE statements?

On 11/15/2015 7:24 PM, Randy Eels wrote: > My main question is: is an 'INTEGER PRIMARY KEY' column guaranteed not to > change, except as a consequence of ordinary UPDATE statements? (And in > particular, not as a consequence of a 'vacuum' statement.) Yes. From the documentation for VACUUM (

[sqlite] Are columns declared as 'INTEGER PRIMARY KEY' guaranteed not to change except from UPDATE statements?

Using SQLite 3.8.7.1. Here and elsewhere is mentioned that the official SQLite documentation includes the line Rowids