Postgres will return too much by default on big tables
What do you mean with "return too much"? That sounds serious.
And I think you give not enough credit for the freedom of the software. Oracle has a great database but it's ridiculously expensive to run even a single instance, and Mysql and BerkeleyDB are pawns in Oracle hands. In my opinion that is a *very* good reason not to use them (I kicked them out when Oracle took them over).
With regard to cdb: its main annoyance is that it is for databases that do not change (this is by design: it's after all named cdb: "constant database"). Perhaps it is fits the OPs requirements but it is often a pain (kicked that out, too ;-))
SQLite is nice but pretty simple (and was and is inspired by PostgreSQL, its author told us at PGCon - see here, the talk by Richard Hipp).
Yeah, I agree: Too many factors to think about :)
And IMHO PostgreSQL does not suck. :)
In reply to Re^4: Need DBM file that holds data up to 50,000 bytes
by erix
in thread Need DBM file that holds data up to 50,000 bytes
by bulrush
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |