Debian Administration

Firebird!!!! Please add this option :-)

With the exception of Oracle (which is apparently a nice long acronym for "One Real Arsehole Called Larry Elison" in case you didn't already know ;-) I've tried all the above (and unfortunately a few more, like MS SQL, Access, Approach, and a few others not worth mentioning), and I have to say that it's nice to see PostgreSQL getting some limelight. Of those listed above, it's by far my favorite DBMS.

One of the reasons I like it so much is that the commandline client is so jam packed with help and hints. The MySQL client is also pretty good, and I do miss "SHOW CREATE ... " although psql's "\d ... " is pretty close.

I've been meaning to get around to trying out Oracle's free "Express" release (and maybe IBM's new "Express" DB2UDB effort), as it's still a frequent requirement in job adverts.

Now all I need to do is play with slony...

Laters.

if its my own server, i prefer to use PostgreSQL. Most of the webhosting services and some of the applications(eg: Wordpress) support only MySQL, so i have to go with it.

"I never let schooling interfere with my education" --Mark Twain

We run SAP on Informix, though we may migrate this to DB/2.

For my own stuff I don't use DBs much so I tend to use SQLite via Perl/DBI when I need a DB, becauss it's easy. I can't say I have a real favourite.
--
"It's Not Magic, It's Work"
Adam

Hi, I am only starting with PostgreSQL now, but if there are more Perl blokes in here you might be interested in the following:

http://www.postgresql.org/docs/current/interactive/plperl.html

I voted MySQL, but I suspect I'm going PostgreSQL in the next couple of months :)

Cheers

Nico

===============================================
=== http://4j.blogspot.com/ ===
=== http://sourceforge.net/projects/lampas/ ===
===============================================

Joh 3:36

It depends upon the task to be performed... if it's mostly select statements with very few inserts and time is the most critical parameter, I use MySQL. If there is a greater balance between inserts and selects and atomicity is important, I use PostgreSQL.

If the load is low, writes infrequent, and the application is more of an embedded nature, then I use SQLite.

Oracle... generally sucks.

g?dbm is occasionally handy, but I've found SQLite to be more friendly.

I hate to call "plain text" flatfiles databases, but I do use them from time to time when I can't justify SQLite or the overhead of a client-server RDBMS.

All this just to say that I don't have a favorite.

For little PHP applications I use MySQL mostly. For other I use PostgreeSQL and at the company we use Oracle and MS SQL. I think both have wonderful features.

-
A programmer is just a tool which converts coca cola into code.

I've been a big fan of PostgreSQL for years, and still recommend (and use) it for large data sets and distributed use.

Recently though, I've found myself using SQLite more and more. In the sort of work I'm being asked to do nothing fits the bill better. This is currently mostly web applications installed on a single server with limited data sets. It's real-world performance is just fantastic and there is absolutely no admisistration overheads. That's a pretty big deal when you are looking after hundreds of databases.

There are caveats of course -- by design it fills a different niche than the MySQL or PosgreSQL. If I ever get a big money/big traffic client (fingers crossed :-) I'll go for a optimised PostgreSQL server on it's own machine. Until that happens, SQLite makes dealing with all the small fry a breeze!

Heheh..
dbm/gdbm is still at zero votes. Can't same I blame anyone :)

-MrFusion