A song for the lovers

In these two days I was looking forward to a Relational DBMS with the following features for my own stuff and also to study it more into deep. The DBMS that I took into consideration are: MySQL, PostgreSQL, FirebirdSQL and MSDE. I admit that is not the whole plethora of RDBMS outta there (the list lacks of “big” names such as Oracle, DB2, SAP DB) but for one reason or another i left them behind (Oracle and DB2 are too big for my own stuff and SAP DB is now part of MySQL suite). I’m not an expert in none of the DBs in the list but I’ve used all of them in the past. The two main features for my own purposes are: cross-platform and C#/Java/Python/other language bindings. So I discarded the MS product, cause, yes, it could be accessed from those languages but it’s definitely not cross platform (I don’t want N DBs combined with the N languages and the N platforms I use; only one DB to rule them all ). My second reject was MySQL cause it lacks of stored procedures, subqueries and some other stuff. Now the game was between PostgreSQL (very good DB, it’s also an OORDBMS) and FirebirdSQL (born from the ashes of the free version of Borland Interbase) but the winner is… FirebirdSQL for some reasons: PostgreSQL is cross-platform (Linux, FreeBSD, MacOSX and other OSes) but not “across” Windows (there isn’t an official, stable port for Win machines); FirebirdSQL is free and open source, it does support Windows, stored procedues, triggers, UDF, SQL-92, has enterprise features (such as hot backup, replication and so on) and has an embeddable library too. So I think I’ve gone right… what do you think?