| |||||||||||||
Firebird adds new features with version 2.1Firebird adds new features with version 2.1Posted Apr 24, 2008 23:15 UTC (Thu) by intgr (subscriber, #39733)Parent article: Firebird adds new features with version 2.1
> Firebird is one of the popular open-source relational database management systems (RDBMS) that runs under Linux. What, where does this come from? As far as I can tell, it's one of the *least popular* open source RDBMSes that run on Linux. Applications that support Firebird are few and far between; You rarely even hear anything about it. Meanwhile MySQL and PostgreSQL are making all the headlines.
(Log in to post comments)
Firebird adds new features with version 2.1 Posted Apr 25, 2008 5:25 UTC (Fri) by nlucas (subscriber, #33793) [Link] Yeah, and SQLite used mostly everywhere else a full RDBMS isn't needed (with every Mac, with every iPhone, with every Firefox install, inside a lot of cell phones, MP3 players, etc). I actually had known it from many years ago (because of the Borland connection), but had forgotten about it until the Firebird/Firefox issue.
Firebird adds new features with version 2.1 Posted May 29, 2008 4:50 UTC (Thu) by jobinau (guest, #52296) [Link] >>Meanwhile MySQL and PostgreSQL are making all the headlines. yes they are making much noice. but still lagging. Mysql is still under development. far behind a matured RDBMS. Postgress is still stucked up in Processes instead of threads. but other than heavy on resources, Postgres is a OK. Firebird is real winner.
Firebird adds new features with version 2.1 Posted May 29, 2008 12:09 UTC (Thu) by nix (subscriber, #2304) [Link] I suspect you don't know what you're talking about. Using processes instead of threads doesn't necessarily make you 'heavy on resources'. It doesn't necessarily indicate that you are 'stuck' in any way at all. It requires greater discipline than using threads, and the context switch time is slightly higher, making it an inappropriate technique for insane loads, but in every other way using processes is *preferable*. Think: what happens if a single MySQL server thread crashes. Who knows what state it corrupted first: best take the whole server down. If a PostgreSQL server crashes, the others are unaffected, their address spaces inviolate save for a strictly-defined shared memory region: they can generally carry on.
|
|||||||||||||