Dmytro Bogovych wrote:
On Fri, 10 Sep 2004 15:31:00 -0400, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
SQLite is using the temporary file to hold a statement-level
rollback journal so that the partial results of the UPDATE
can be rolled back if it encounters an error half way through.
You can circumvent this by doing
UPDATE OR ROLLBACK
log:
SQLite version 3.0.6
Enter ".help" for instructions
sqlite> begin;
sqlite> update or rollback ITEMS set number=number+1 where number>2;
-- here is breakpoint triggering --
OK. My workaround trick didn't work afterall. Looks like you
are stuck with a temporary file when doing an UPDATE or a mass
INSERT inside a transaction.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
