> 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.
MySQL lets you fiddle.....
mysql> create table tt (id int NOT NULL AUTO_INCREMENT, v TEXT, PRIMARY
KEY(id)) ;
Query OK, 0 rows affected (0.11 sec)
mysql> insert into tt (v) VALUES("one");
Query OK, 1 row affected (0.00 sec)
mysql> select * from tt;
+----+------+
| id | v |
+----+------+
| 1 | one |
+----+------+
1 row in set (0.00 sec)
mysql> update tt set id=10 where id=1;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1 Changed: 1 Warnings: 0
mysql> select * from tt;
+----+------+
| id | v |
+----+------+
| 10 | one |
+----+------+
1 row in set (0.00 sec)
mysql> insert into tt (v) VALUES("one");
Query OK, 1 row affected (0.00 sec)
mysql> select * from tt;
+----+------+
| id | v |
+----+------+
| 10 | one |
| 11 | one |
+----+------+
2 rows in set (0.00 sec)
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by
Mimecast.
For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
