Re: [sqlite] Long time to drop tables.

On 19 Aug 2014, at 11:41am, Jonathan Moules wrote: > There are some foreign keys. Put all your DROP TABLE commands into one big transaction. Make sure when you DROP your TABLES that you are dropping them in an order which won't trigger any foreign key

Re: [sqlite] Long time to drop tables.

HI, Thanks for the replies. The entire thing on happening on a single desktop machine. The database is on a standard HDD. Using SQLiteStudio; sqlite version 3.7.16.1. There are some foreign keys. Autovacuum is off I think (don't know how to check, but the table size never automatically shrinks

Re: [sqlite] Long time to drop tables.

On Sat, Aug 16, 2014 at 2:41 PM, Jonathan Moules < jonathanmou...@warwickshire.gov.uk> wrote: > Hi List, > More of a curiosity. > I'm doing some general data munging and set off a query that consists > entirely of 37 DROP TABLEs in it. The database it's running against is > a bit less

Re: [sqlite] Long time to drop tables.

t;Subject: [sqlite] Long time to drop tables. > >Hi List, > More of a curiosity. >I'm doing some general data munging and set off a query that consists >entirely of 37 DROP TABLEs in it. The database it's running against is >a bit less than 1GB made of about 5 million

Re: [sqlite] Long time to drop tables.

On 16 Aug 2014, at 7:41pm, Jonathan Moules wrote: > My questions is - why does it take so long? The total time required > to create this dataset (most of which was processing on the Python > side) was about 11 minutes. > > The total time

[sqlite] Long time to drop tables.

Hi List, More of a curiosity. I'm doing some general data munging and set off a query that consists entirely of 37 DROP TABLEs in it. The database it's running against is a bit less than 1GB made of about 5 million rows, and the tables being dropped constitute about 99% of the content.