Slashdot Mirror

← Back to Stories (view on slashdot.org)

MySQL's Response to Oracle's Moves

Posted by ryuzaki0 on from the the-changing-world dept.

mAriuZ writes "I've recently written two articles on this topic for Database Journal, the earlier, written after the InnoDB purchase, entitled Oracle's purchase of InnoDB, their release of Oracle Express, and the effect on MySQL, and the most recent, just after the Sleepycat purchase, entitled Pressure on MySQL increases as Oracle purchases Sleepycat, with more to come. Since I only do a monthly column for Database Journal, and things change quite quickly, I thought I'd post a few more thoughts on the topic."

2 of 194 comments (clear)

  1. Re:Let's hope the best by bigtrike · · Score: 0, Troll

    The TIMESTAMP data type has varying properties, depending on the MySQL version and the SQL mode the server is running in. These properties are described later in this section. http://dev.mysql.com/doc/refman/5.1/en/datetime.ht ml

    You expect good work from the same people who wrote such poorly planned code that it necessitated this kind of text in the manual? Even if MySQL wasn't a featureless pile of garbage, it's only really usable for in house and GPL applications due to licensing restrictions.

  2. Go PostgreSQL! by nbritton · · Score: 0, Troll


    This would be the best thing to ever happen to PostgreSQL, MySQL is a POS.