K5 is not a serious database application. We have about two JOINs in the code, total. We have no transactions. We don't do any fancy database stuff. Mostly it's just supposed to be a fast data bucket.
IMHO, serious database application has far more to do with performance (specifically in highly-concurrent situations) than query syntax support.
Writing query parsers is easy, and the trivial implementation of the SQL command set is very simple to implement. Making it go fast (even on the simple queries) is the hard part ;)
I still can't figure out why people have such an obsession with Postgres, when mysql is easier to use and works just as well. ;-)
Transactions, scalability, ACID.
Actually, ever since they added BerkeleyDB tables (less than a year ago, I think), I started considering the combination of the two a "real" database. BerkeleyDB, despite not having SQL support, was always far more of a database than MySQL ever was to begin with ;) MySQL isn't much more than a query parser for BerkeleyDB in that sort of configuration ;)
If you disagree, and somebody has already posted the exact rebuttal that you would use: moderate, don't post.
[ Parent ]