NSRT Mail account. <joecool2...@yahoo.com> wrote: > The entry in meetings is now gone. Should ON DELETE CASCADE be picking up an > UPDATE as a DELETE via INSERT INTO from ON CONFLICT > REPLACE?
REPLACE involves deleting conflicting rows, followed by INSERT, as explained by the documentation at http://sqlite.org/lang_conflict.html . No UPDATE is taking place - in general, several rows may be deleted for one row inserted, in which case update would make no sense. > Is there perhaps a better way I should be structuring my tables so I can use > an INSERT or UPDATE style command, yet force DELETEs > to cascade to the other table? What problems do you have with UPDATE? This should work: UPDATE users set name='Joe C' where id=1 and type=4; -- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
