Re: why postgres? SQLite is the way to go!

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: why postgres? SQLite is the way to go!
by David on Wednesday 23/Feb/2005, @14:06

There are some issues with using SQLite which I think Scott has gone over above. For what SQLite does it is very, very good, but probably not what they're looking for for the purpose of this.

However, if you've ever built KDE you'll know just how many other projects KDE depends on. Postgres is actually small-fry compared to the total.

Related Links

·   Articles on Community and Events
·   Also by David
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: why postgres? SQLite is the way to go!
by ac on Wednesday 23/Feb/2005, @18:45

I really don't care what database backend an application uses, but it would be nice if I didn't have to run 5 different DB servers in the background just to use KDE.

[ Reply To This | View ]

Re: why postgres? SQLite is the way to go!
by Ian Monroe on Thursday 24/Feb/2005, @00:20

This is a very valid point... kdelibs requiring a database (which it sounds like it will be doing) will make things a lot easier for a variety of KDE programs that currently have to come with packaged with sqlite.

[ Reply To This | View ]

Re: why postgres? SQLite is the way to go!
by Aaron J. Seigo on Thursday 24/Feb/2005, @00:21

> but it would be nice if I didn't have to run 5 different DB servers in the
> background just to use KDE

i don't think you will. at most you may have to run one, and even that may well turn out to be optional (at the cost of the features that rely on it).

[ Reply To This | View ]

Re: why postgres? SQLite is the way to go!
by Arun Raghavan on Friday 02/Sep/2005, @20:06

While my first reaction was, "*Groan*, WhyTF do I need to run a DB server on my PC just to have a good desktop experience", I think this is a good decision. Modern systems will not be loaded excessively by a Postgres server running in the background, and the payoff would be *much* more than worth it.

But I do wish it could all be independent of the actual database used. Or at least give a choice between 2-3 popular databases. Maybe eventually, closer to productization, when such pragmatic issues are more important.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"Never miss an opportunity to throw away code." -- Guillaume Laurent
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.