I think you could also just defer foreign key checking to the end of the transaction.
On 2016/01/20 12:20 PM, chromedout64 at yahoo.com wrote: > The problem with REPLACE is: " the REPLACE algorithm deletes pre-existing > rows that are causing the constraint violation prior to inserting or updating > the current row" > > When using REPLACE with a table containing a foreign key clause ON DELETE > CASCADE causes data in other tables to be deleted. > > Postgres recently implemented the UPSERT command in 9.5. I was just wondering > if SQLite will decide to implement it or not, or if there is some reason they > have chosen not to. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
