Bug#301883: asterisk: sqlite logging enabled by default and never
Mon, 04 Apr 2005 23:14:00 +0300
On Mon, Apr 04, 2005 at 09:32:31PM +0200, Kilian Krause wrote:
> Hi Jose,
> > > Or simply: purge all records older than a month.
> > Yes, that should work, IMO. I though about using sql after writing my
> > previous mail to this bug. The problem with this is that I am quite bad
> > with sql (I actually don't know the language) so if someone could write
> > the "query" to use...
> the query would be something like "delete from $mytable where
> $insertdate < $(today-1month)" with the variables holding the correct
> names etc.
> Yet I strongly disagree with this behaviour for a default. At least the
> 1 month rollback sounds like too few from a data-warehouse point of view
> and too much from a duty of secrecy point of view. The only real
> alternative sounds to be a debconf asking for the proper length.
> Does that sound ok for everybody?
What about archiving older data? Is it possible to create an (gzipped?)
Then it can be made part of logrotate, and the user will be able to
decide the time. And this may even be triggered by size.
Anyway, I want to build asterisk packages with asterisk-sqlite so that
if someone is already using CSV, there won't be a surprise about CDR
suddenly not working.
Tzafrir Cohen icq#16849755 +972-50-7952406