If I understand the docs correctly, the REPLACE part of an INSERT OR REPLACE command deletes a row if a UNIQUE constraint occurs and inserts a new row in its place. On the face of it, that seems like it will invalidate any foreign key definitions that use the primary key of the INSERT OR REPLACE table as a parent link, and it doesn't feel like ON DELETE or ON UPDATE actions can handle that situation.
Is there a way to deal with this situation or should I not use INSERT OR REPLACE on a table that is the parent of a foreign key definition? Pete lcSQL Software <http://www.lcsql.com> _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
