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

[Matthias Schniedermeyer <ms@citd.de>]

On Sun, Apr 07, 2002 at 07:08:54PM +0200, Henning Holtschneider wrote:
> ----- 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.

Documentation is one of my weakest points. I wish i had a "ghostwriter".

> Instead of using yet another method to store its data, my personal
> wish for master-timer would be a cleaner version with better
> documentation :-)

I wish that too. ;-)

> 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?

I don't understand your problem.

Do you mean that no timer at all is programmed. (Including epg-data that
is "fresh". (I mean epgdata from "next morning" when a new day comes
into the epgdata))



Btw. I wish that people send email when they have problems. :-)




Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.