Integrity check is ok. I'm deleting using primary keys only, so it shouldn't be an index problem either.
----- Original Message ----- From: Simon Slavin <slav...@bigfraud.org> To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Sent: Wednesday, March 27, 2019, 19:25:17 Subject: [sqlite] Row locking sqlite3 On 27 Mar 2019, at 6:04pm, Thomas Kurz <sqlite.2...@t-net.ruhr> wrote: > Ok, well.... very interesting and I'd never have had this idea, but indeed it > works: within a transaction, it takes only a few seconds. This is very > surprising as to me, a single DELETE statement is nothing more than that: a > single atomic operation which should automatically be treated as a > transaction (auto-commit-mode). I don't think this is the problem. I think it's more likely the other problem I mentioned: difficulty in finding which cascade rows to delete. Did you run your integrity check and make sure you had an appropriate UNIQUE index (or that you were keying on your primary key) ? Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
