On Tue, 28 Jun 2016 19:19:43 -0700
J Decker <d3c...@gmail.com> wrote:
> Duplication can also result as part of the - in process - moving of
> rows. To change the order of [1,2,3,4] to
> [1,3,2,4] there is(can be) a state that is [1,2,2,4] before the
> second part that sets three back into 2.
I'd just like to point out to the OP that, while SQLite does behave in
the way described above, it's a flaw. SQL semantics are
per-statement, not per-row. From an SQL perspective, any "state" that
might occur within a statement is meaningless.
In SQLite, an update to a primary key K fails
update T set K = K + 1;
if, for any value v in K, there exists v + 1. By the rules of SQL, it
should succeed and, in most other DBMSs, does.
--jkl
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
