Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vdr] Re: DELT: unexpected behaviour
On Wed, Jan 28, 2004 at 10:54:01PM +0100, Klaus Schmidinger wrote:
> Sergei Haller wrote:
> >
> > hello,
> >
> > I remembered reading this:
> >
> > DELR <number>
> > Delete the recording with the given number. Before a recording can be
> > deleted, an LSTR command must have been executed in order to retrieve
> > the recording numbers. The numbers don't change during subsequent DELR
> > commands. ..."
> >
> > so I supposed that DELT has the same behaviour. Unfortunately not:
> > (as you can see on the number of colons, I made a copy&paste mistake while
> > entering the following two timers)
> >
> > lstt
> > 250-...
> > 250-11 1:10:4:0028:2204:9:99:99:Stephen Kings The Stand~Teil 2:
> > 250 12 1:10:11:0004:0028:2204:9:99:99:Stephen Kings The Stand~Teil 3:
> > delt 11
> > 250 Timer "11" deleted
> > delt 12
> > 501 Timer "12" not defined
> >
> > It's not a big problem. it was just unexpected. would be nice if DELT,
> > DELT and DELC would have the same behaviour.
>
> I'll keep this in mind when extending the SVDRP interface to allow
> multiple SVDRP connections. Then I'll need to make sure that DELT
> and others like that don't interfere between differnt SVDRP sessions,
> anyway.
I only see
ACID
You have the typical Database problem. Current situation could be
compared to MySQL and MyISAM-Storage. :-)
(Which is not ACID complient)
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.
--
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.
Home |
Main Index |
Thread Index