[RFC]: KConfigSQLBackend

[Caleb Tennis]

On Wednesday 12 March 2003 18:52, Waldo Bastian wrote:
> Does that first step make sense? I think you would like to be able to say
> on a KDE-wide scale "Use the SQL backend instead of the .ini files" I don't
> see the point of using this only for programs specially designed for it.

Perhaps not.  I'm still a little unsure how to handle all of the possible 
scenarios,  but I figure it will unfold as we progress.

> More seriously though, I would very much like to see an implementation of
> this. I'm especially interested in the performance part. I'm somewhat
> afraid that the solution that you outlined may be rather slow. I myself
> played with the idea to keep the INI-Backend but have a file-requester
> service that downloads and uploads config files when needed. The
> applications themselves would then still access the (downloaded) files from
> local disk. The advantage of this approach would be that it might also work
> for files that aren't strictly config files (e.g. the history file of
> konqueror)

The slowness isn't much of an issue for me locally, but I can say that 
performing many queries takes its toll.  One thing I've been using here quite 
successfully is a separately threaded class that actually handles the reads 
and writes.  QThread is used pretty sparingly throughout kdelibs, and I'm not 
sure if that's due to some specific reason not to want to use it, but it 
would definitely keep things lively while the queries were running.

> Anyway, I would like to see this ending up in CVS

Good.  I'll start working on taking what I've got and integrating it with the 
KConfig model.

Caleb