in reply to SQLite vs Firebird vs ...
gone Postgres for almost everything nowadays [...]
Does anyone have experience with Firebird to share?
And there you have it; you really said it yourself in a nutshell. I'd be somewhat interested in firebird too. But who is going to mess with a relative unproven option like firebird? (except perhaps for the embeddedness -- which Pg does not offer)
IMHO, even if one assumes that firebird can catch up with postgres at all, it would take quite some time before it will be able to match postgres' stability and 'ecosystem'.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: SQLite vs Firebird vs ...
by erix (Prior) on Mar 29, 2013 at 09:20 UTC | |
Drifting a bit off-topic perhaps, but I thought this was interesting (we love lists after all, and both your (lightweight?) db's are in the list too). Below is this month's list from a (apparently) monthly updated list of database "popularity" (measured by mentions on google, bing, by job offers, and some other things).
I haven't looked much at the scoring precedure yet. There is the expected top-3, with the expected downward trend of "Big" Oracle. That the trend of "Small" Oracle (=mysql) is still upward is therefore surprising. (Then again, these numbers are over a single month; I should probably look further back for real trends) There is a huge gap between mysql and postgres, numbers 3 and 4. One would expect that that gap is closing; this is obviously not happening in these month's numbers. Ah well... PostgreSQL has overtaken both DB2 and MS-Access in the last 6 months. Surprising, as I had expected DB2 to be much higher on any such list. Anyway, the whole list is here. (They also seem to publish blog posts discussing the changes every now and then, like here) | [reply] [d/l] |
|
Re^2: SQLite vs Firebird vs ...
by sedusedan (Pilgrim) on Mar 12, 2013 at 16:37 UTC | |
Although I usually use Postgres now, embedded/serverless mode still has its uses, for example when a program which is run by normal users wants to store data/statistics in some relational database without having to deal with system-level permissions or a system-wide daemon. Another approach would be to run a per-user database daemon, like in KDE's akonadi which starts its own MySQL daemon; this is not really feasible for a command line-based program. Firebird is not unproven, it has a long (as in decades-long, in some form or another) track record. Though perhaps it's still not popular in Unix/Linux circles. Kind of sad, because SQLite really sucks "SQL-wise". I think I'll bite my finger and just start to use it. I'll share my experiences later. | [reply] |
by Your Mother (Archbishop) on Mar 12, 2013 at 18:32 UTC | |
SQLite really sucks "SQL-wise". SQLite rules for what it is: an utterly free, stable, embeddable, minimalistic engine. Saying it sucks because it doesn't match your use case is like saying a saw sucks because it won't drive nails well. | [reply] |
by sedusedan (Pilgrim) on Mar 13, 2013 at 03:00 UTC | |
| [reply] |
by core_dumped (Acolyte) on Jul 09, 2013 at 01:40 UTC | |
| [reply] |