On 5 Sep 2013, at 7:20pm, Peter Haworth <p...@lcsql.com> wrote: > That works fine but wondering if there might be a single UPDATE statement > that could do this for me. I can use the WHERE clause to select sequence > 3,4, and 5 but the UPDATE has to process the rows in descending sequence > order to avoid UNIQUE conflicts.
An interesting point. If all the updates are done inside a COMMIT, then the conflict may not be recognised because by the time the first change is written back to the table, the conflicting entry has already been renumbered. Nope, apparently SQLite doesn't support deferring conflict resolution until the COMMIT [1]. Maybe that should be added to these two pages: <http://www.sqlite.org/omitted.html> <http://www.sqlite.org/conflict.html> Simon. [1] Except for FOREIGN KEYS. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
