D. Richard Hipp wrote:
>> Though if your db has reached a steady-state size you might consider
>> running a VACUUM just *before* deleting the records, to avoid peaks
>> persisting ... and even then (say) every *other* week.
>> Just a thought !
>>
> VACUUM also defragments a database file
On Oct 27, 2008, at 7:34 AM, MikeW wrote:
> Mohit Sindhwani <[EMAIL PROTECTED]> writes:
>
>>
>> Cory Nelson wrote:
>>> vacuum shrinks the database size by removing empty pages. sqlite
>>> will
>>> normally reuse empty pages - so vacuum is only useful if you don't
>>> plan to insert anything
Mohit Sindhwani <[EMAIL PROTECTED]> writes:
>
> Cory Nelson wrote:
> > vacuum shrinks the database size by removing empty pages. sqlite will
> > normally reuse empty pages - so vacuum is only useful if you don't
> > plan to insert anything else, otherwise it will be slower.
> >
>
> Thanks
Cory Nelson wrote:
> On Sun, Oct 26, 2008 at 8:17 PM, Mohit Sindhwani <[EMAIL PROTECTED]> wrote:
>
>> I'm setting to to delete a bunch of old records ever 2 weeks in a cron
>> job and initially I just wanted to do delete * from table where
>> datetime(created_on, 'localtime') < some_date.
>>
>>
On Sun, Oct 26, 2008 at 8:17 PM, Mohit Sindhwani <[EMAIL PROTECTED]> wrote:
> I'm setting to to delete a bunch of old records ever 2 weeks in a cron
> job and initially I just wanted to do delete * from table where
> datetime(created_on, 'localtime') < some_date.
>
> Then, I remembered about
5 matches
Mail list logo