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

List:       kde-pim
Subject:    Re: [Kde-pim] Proposal: KSharedFile
From:       Andrew Sutton <ansutton () sep ! com>
Date:       2001-12-14 0:30:56
[Download RAW message or body]

On Wednesday 12 December 2001 07:32 pm, Preston Brown wrote:
> On Wed, 2001-12-12 at 18:39, Nick Papadonis wrote:
> > Has anyone had any experience with Berkeley DB?
>
> Yup. (Me.)
>
> SQL is probably overkill for this.

there's an alternative option... you could push the actual decision of what 
db to use to run time using the Qt database stuff. granted, it might take 
some work, but you could define database drivers of ther berkely db or a flat 
file so all your queries look the same.

if you're installation wants to use an enterprise DB, then it should just be 
a configuration option. for most users a flat file or personal db (berkeley) 
would suffice - also a command line option.

anyway, that might not necessarily resolve all the issues about what kind of 
capabilities the underlying persistent store needs, but it does provide a 
nice abstraction that lets you replace the underlying DB.

besides, the qt db stuff is really pretty smooth. take a look :)

andy
_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
[prev in list] [next in list] [prev in thread] [next in thread]