On 1 Nov 2016, at 10:45am, R Smith <rsm...@rsweb.co.za> wrote: > D - Horrible if you up some key value significantly and then update it back > down, because there is no way the Autoinc value should *EVER* be able/allowed > to come back down. It's a one-way street.
This is an additional argument for not allowing UPDATE to change an "INTEGER PRIMARY KEY AUTOINCREMENT" value. Which, according to GB, is what some other SQL engines do: attempts to change a value in that column using UPDATE always generate an error. I didn't know that. I looked it up. Apparently Microsoft's SQLSERVER blocks it, but I was unable to find anything mentioning how any of the other big SQL engines handles it. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
