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

List:       kde-devel
Subject:    Re: sqlite in kdelibs
From:       Renchi Raju <renchi () gmail ! com>
Date:       2004-12-29 18:43:39
Message-ID: 1bad0cda041229104399c1070 () mail ! gmail ! com
[Download RAW message or body]

On Wed, 29 Dec 2004 04:45:44 +0100, Dirk Mueller <mueller@kde.org> wrote:
> On Wednesday 29 December 2004 01:29, Renchi Raju wrote:
> 
> > additional reasons (the primary ones why we at digiKam include sqlite
> > in our code):
> 
> .. still, the correct way would be to fix the bugs regarding sqlite in Qt and
> use the Qt version, instead of adding yet another fork of it.

its not a fork. two config.h options... which many distros forget to turn on. 

And, there is a difference between amarok and digikam when it comes to
using an external sqlite. for us, once you lose the metadata, its gone
forever. in case of amarok, they can always retrieve it back from the
files (i believe they recently upgraded to sqlite3 from sqlite2, by
throwing away the old metada and rereading from the files). So for us,
making sure that the metadata is correctly restored across version
upgrades is very important, which is not guaranteed by using an
external sqlite library.

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