[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KConfig SQL backend
From:       Cornelius Schumacher <schumacher () kde ! org>
Date:       2008-07-22 8:30:11
Message-ID: 200807221030.11925.schumacher () kde ! org
[Download RAW message or body]

On Tuesday 22 July 2008, Ivan Vasin wrote:
> An SQL-backed configuration backend was incidental to another project
> I am working on, so I decided to write a plugin for KConfig which uses
> an SQL database instead of the INI-like files used by
> KConfigIniBackend. Specifically it uses Qt's database abstraction
> layer provided by QSqlDatabase and QSqlQuery. The implementation I
> wrote, KConfigMysqlBackend, is hardcoded for MySQL, but creating other
> implementations for any other SQL driver supported by Qt is simply a
> matter of changing "QMYSQL" to something else in the constructor. If
> it could be rewritten as a "KConfigSqlBackend" which somehow accepted
> a parameter to select the SQL driver, that would be better, but I
> don't know how to do this.

Interesting work. What's the advantage of a SQL backend over the file backend? 
How does it compare performance-wise?

-- 
Cornelius Schumacher <schumacher@kde.org>
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]