Re: [sqlite] possible integrity problem

2017-01-15 Thread Kevin O'Gorman
On Sat, Jan 14, 2017 at 5:04 PM, Simon Slavin wrote: > > On 15 Jan 2017, at 1:01am, Kevin O'Gorman wrote: > > > Update: the integrity check said "ok" after about 1/2 hour. > > the record count now takes about 4 seconds -- maybe I remembered wrong >

Re: [sqlite] possible integrity problem

2017-01-14 Thread Richard Hipp
On 1/14/17, Simon Slavin wrote: > > Given your 5 indexes, 30 minutes to check an 11GB file is completely > reasonable. Don’t worry about that. > PRAGMA integrity_check looks into a lot of detail - such as verifying that every entry in the table has the correct

Re: [sqlite] possible integrity problem

2017-01-14 Thread Simon Slavin
On 15 Jan 2017, at 1:01am, Kevin O'Gorman wrote: > Update: the integrity check said "ok" after about 1/2 hour. > the record count now takes about 4 seconds -- maybe I remembered wrong and > it always took this long, but I wasn't stopping it until it had hung for >

Re: [sqlite] possible integrity problem

2017-01-14 Thread Kevin O'Gorman
Update: the integrity check said "ok" after about 1/2 hour. the record count now takes about 4 seconds -- maybe I remembered wrong and it always took this long, but I wasn't stopping it until it had hung for several minutes. Color me baffled. On Sat, Jan 14, 2017 at 4:49 PM, Kevin O'Gorman

[sqlite] possible integrity problem

2017-01-14 Thread Kevin O'Gorman
I've got a database that has acted strangely from time to time. Or actually a series of them, since I erase and build from scratch sometimes, as I'm just starting this project. Anyway, the latest is that the DB is about 11 GB. It's pretty simple, just 2 main tables and maybe 5 indexes, no