Hello ! Thanks for reply !
That's why I said that vacuum and maybe other operations need to interpret the parameter passed to? sqlite3_progress_handler differently otherwise a setting that works on general case do not work with then, maybe a mix of number of operations/time ? Cheers ! > Thu Mar 17 2016 08:51:11 PM CET from "Richard Hipp" <drh at sqlite.org> >Subject: Re: [sqlite] sqlite3_progress_handler do not seem to be called >byvacuum > > On 3/17/16, Domingo Alvarez Duarte <sqlite-mail at dev.dadbiz.es> wrote: > >>Hello ! >> >> Hello I have an application that uses sqlite3_progress_handler to update a >> gui application and when we do a "vacuum" on a big database the gui get >> frozen, maybe vacuum should use different parameters to call >> sqlite3_progress_handler I'm using actually: >> >> db.progress_handler(1000, sqlite3_progress_handler, this.weakref()); >> >> And with a 1000 as parameter it works fine for select. >> >> Sqlite3 is really calling sqlite3_progress_handler ? Or it's not >> implemented >> there ? >> >> > Vacuum works by running a bunch of secondary SQL statements. Each of > these secondaries has its own progress counter. So, in other words, > the progress counter is not cumulative for a VACUUM. Maybe your 1000 > is set to high and none of the many secondary SQL statements ever hit > the limit. > -- > D. Richard Hipp > drh at sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > > ?
