faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: why postgres?
by Scott Wheeler on Thursday 24/Feb/2005, @08:06
|
> we (amarok) have dealed with quite all sqlite issues you could imagine
Honestly I doubt it. amaroK is a very simple application (in database terms) relative to what we're working on. A music player with a couple MB of data is a very different beast trying to store and query graphs in a database that may easily grow to a few hundred MB.
> why not use a singleton interface for searching?
Because that's only useful for one process.
> most sqlite issues can be easily solved by setting proper indices
Not for heavy use of cross table selects on interrelated values. I literally had several queries that took 15 minutes on SQLite that were done in less than 1-2 seconds on PGSQL or MySQL. And that was just on a 10 MB test database. I'm not saying that the limitations of SQLite couldn't possibly be worked around, I'm just saying that there's no compelling reason to work around them when there are better databases available that already solve these problems.
SQLite also locks the entire database on write, which just isn't acceptable in a tool used frequently by multiple processes.
Basically, as Aaron already said -- it might be possible to work around all of the issues with SQLite. But in the end we'd just be implementing the features that other databases already provide and we'd need a daemon process anyway to handle communication with it, which, well, makes no sense. |
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
