I'm a MySQL veteran, but...
The majority of my coding life has been spent with two tools.
I don't claim to be a guru programmer, but the various professional problems which have been presented to me have always found their solution using these two tools. They're great tools. *sigh*
Recently I've found out that Oracle
owns both sleepy cat's db engine "bdb
" and Innobase's as well (innodb
). I have *no* idea if this presents any potential problems as far as conflicts of interest go, but it caused me to have some serious doubts. I only recently found out about this, and know *nothing* of the intentions of Oracle's purchase, but I felt like blogging before researching, so you're getting a pretty uninformed blog entry. But that's all besides the point.
As of about a year ago (more or less), I've been hearing good things about a db engine called Postgres
from my good friend Steve
. Well, I've been doing a bit of piddling about with Postgres on my own, and I've found it to be at least a worthy candidate for dabbling, and from what I hear, it's a pretty darned robust, as well as featureful db engine.
I think I'm gonna get a bit more serious about Postgres due to various, mostly biased, worries I have about MySQL. Also, at work, MySQL is starting to be stretched a bit, and I really don't know much about optimizing it to handle 500,000+ rows per table.
Anyway... There's your blog for the month. :)