On 1 Jan 2014, at 9:55pm, James K. Lowden <jklow...@schemamania.org> wrote:
> sqlite> update i set i = random(); Yeah. You have to do it properly. Mark the rows which will be obsoleted, make up the new rows, and check the resulting union for consistency. Which means that you need to temporarily have enough memory (or filespace) free for all the new rows. Hmm. Even update t set i = i + 1 - 1 with i being UNIQUE might be a good test case. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
