[vdr] Re: Should Master-Timer use a Database?

["Henning Holtschneider" <hh@holtschneider.com>]

----- Original Message -----
From: "Matthias Schniedermeyer" <ms@citd.de>
To: <vdr@linuxtv.org>
Sent: Friday, April 05, 2002 10:54 PM
Subject: [vdr] Should Master-Timer use a Database?


> Currently i ask myself if i could/should convert Master-Timer to use a
> database (mysql) as a backend for storing information. (epg-data,
> timer-info, configuration ...)

I don't really like that idea. This would require a fully-featured database
somewhere (on the network or on the VDR machine itself) which requires a lot
of resources. As Alessio Sangalli suggested earlier, I would prefer XML. But
if you insist on using a database, please don't use any database-specific
functions/queries.

Matthias, please don't get me wrong on this. I don't want to offend you and
I certainly wouldn't haven written the program much different - but from my
point of view, it's time to fix bugs :*) I've been using master-timer for
quite a while and every version I installed had either showstopper bugs or I
misinterpreted the various configuration files. The documentation is bad and
it's a headache to understand the sourcecode and how the various scripts fit
together. Instead of using yet another method to store its data, my personal
wish for master-timer would be a cleaner version with better documentation
:-)

hh

P.S. Does anyone know why master-timer 0.5.1 stops setting timers after a
couple of days if I don't delete the program.dat file?