I believe it's basically saying that the way it's implemented, vacuum can't be rolled back, and therefore can't be done in the middle of a transaction, it has to be on its own.
-----Original Message----- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Simon Slavin Sent: Monday, April 01, 2019 9:47 AM To: SQLite mailing list Subject: Re: [sqlite] importing a large TSV file On 1 Apr 2019, at 2:41pm, Simon Slavin <slav...@bigfraud.org> wrote: > BEGIN; > ... CREATE all your INDEXes ... > VACUUM; -- optional > END; Apologies. The documentation says "A VACUUM will fail if there is an open transaction" I'm not sure whether this means that VACUUM must be outside the transaction, like the particular PRAGMA I used. So it would better to move the VACUUM after the END. _______________________________________________ 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
