Roland Wilczek wrote: > - If two foreign keys come into conflict, SQLite silently ignores one of them > instead of raising an error. > > CREATE TABLE track (artist, > FOREIGN KEY (artist) REFERENCES artist(id) ON DELETE CASCADE > FOREIGN KEY (artist) REFERENCES artist(id) ON DELETE RESTRICT);
SQLite allows pretty much anything inside a CREATE TABLE statement, and ignores anything it doesn't recognize. This particular statement creates a table with a single foreign key constraint. Table constraints must be separated with commas. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
