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.

In reply to Re^2: SQLite vs Firebird vs ... by sedusedan
in thread SQLite vs Firebird vs ... by sedusedan

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.