基于SQLite foreign key documentation，它应该是创建两个数据库的方式，并且如果父字段得到更新，引用父字段的字段也会更新。

问题：一旦我按照下面的步骤操作，一切正常，直到最后一条命令

SELECT * FROM track;，因为结果仍然保持不变，因此它应该变成最后显示的结果。

trackid trackname trackartist

------- ----------------- -----------

11 That's Amore 1

12 Christmas Blues 1

13 My Way 2编码：

-- Database schema

CREATE TABLE artist(

artistid INTEGER PRIMARY KEY,

artistname TEXT

);

CREATE TABLE track(

trackid INTEGER,

trackname TEXT,

trackartist INTEGER REFERENCES artist(artistid) ON UPDATE CASCADE

);

sqlite> SELECT * FROM artist;

artistid artistname

-------- -----------------

1 Dean Martin

2 Frank Sinatra

sqlite> SELECT * FROM track;

trackid trackname trackartist

------- ----------------- -----------

11 That's Amore 1

12 Christmas Blues 1

13 My Way 2

sqlite> -- Update the artistid column of the artist record for "Dean Martin".

sqlite> -- Normally, this would raise a constraint, as it would orphan the two

sqlite> -- dependent records in the track table. However, the ON UPDATE CASCADE clause

sqlite> -- attached to the foreign key definition causes the update to "cascade"

sqlite> -- to the child table, preventing the foreign key constraint violation.

sqlite> UPDATE artist SET artistid = 100 WHERE artistname = 'Dean Martin';

sqlite> SELECT * FROM artist;

artistid artistname

-------- -----------------

2 Frank Sinatra

100 Dean Martin

sqlite> SELECT * FROM track;

trackid trackname trackartist

------- ----------------- -----------

11 That's Amore 100

12 Christmas Blues 100

13 My Way 2为什么是这样？