It's the Postgres Age

Re:It's the Postgres Age by DavidAbrams on Wednesday May 23, 2012 @03:07PM (#4014744)

It took what, five years to fix the glaring design flaw where you couldn't use NOW() as the default in a datetime field. Seriously, this was just fixed a few weeks ago after years of outrage over it, and it was fixed by an outsider: http://bugs.mysql.com/bug.php?id=27645 Now we all get to wait for our hosts to update their MySQL installation, once the fix makes it into a release. How many more years will that be?

If it has any significant deficit, MySQL is not going to "catch up." I'm not necessarily agreeing with the article, but don't fool yourself.

[ Parent | on HN ]

Re:It's the Postgres Age by adventureful on Wednesday May 23, 2012 @03:39PM (#4014912)

Last time I checked, MySQL isn't governed by fate. What happened three years ago (or a year ago etc) has absolutely nothing to do with what the MySQL team does tomorrow in regards to improving the software.

If things actually worked that way, Windows 7 would have been worse than Vista, and the quality of iTunes today would ensure Apple could not compete for the future of the music market.

[ Parent | on HN ]

Re:It's the Postgres Age by DavidAbrams on Wednesday May 23, 2012 @10:08PM (#4016414)

We're talking about TURNAROUND TIME, not what happened years ago. This is something that took five years TO happen.

[ Parent | on HN ]