Hi,
Am Samstag, den 09.09.2006, 11:51 +0200 schrieb Rene Bartsch:
> if the configuration (channels, transponders, options) and EPG would
> be stored in a MySQL-DB other applications could easily use that data
> instead of doing expensive scans of the files again and again.
There exits XXV, it sto
> It does have the added overheads of running MySQL on what might be a
> low-power
> system, slower startup, etc. Then again, reading large amounts of EPG
> data,
> etc. from what can be huge flat files should improve things!
>
> Maybe it could be a build-time option...
>
Maybe embedded SQL can he
> Rene Bartsch wrote:
>> if the configuration (channels, transponders, options) and EPG would be
>> stored in a MySQL-DB other applications could easily use that data
>> instead
>> of doing expensive scans of the files again and again.
>>
>> Maybe there could be a compiler switch or even a command
On Saturday 09 September 2006 12:09, Christian Wieninger wrote:
> Rene Bartsch wrote:
> > if the configuration (channels, transponders, options) and EPG would be
> > stored in a MySQL-DB other applications could easily use that data
> > instead of doing expensive scans of the files again and again.
Rene Bartsch wrote:
if the configuration (channels, transponders, options) and EPG would be
stored in a MySQL-DB other applications could easily use that data instead
of doing expensive scans of the files again and again.
Maybe there could be a compiler switch or even a command-line option for
V
Rene Bartsch wrote:
Hi,
if the configuration (channels, transponders, options) and EPG would be
stored in a MySQL-DB other applications could easily use that data instead
of doing expensive scans of the files again and again.
Maybe there could be a compiler switch or even a command-line option
