Re: [OT] MySQL is bad, but THIS bad?

From: John DeSoi <desoi(at)pgedit(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: Mark Woodward <pgsql(at)mohawksoft(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [OT] MySQL is bad, but THIS bad?
Date: 2006-05-18 16:48:47
Message-ID: C5C52BDD-7FCD-4241-9855-071EB974ED8F@pgedit.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-hackers


On May 18, 2006, at 12:24 PM, Jim C. Nasby wrote:

> Even better would be coming up with a compatability mode, a la what
> EnterpriseDB has done for Oracle.

Right, you'll definitely need to hack the C source code to force
PostgreSQL to accept invalid dates ;)

http://sql-info.de/mysql/gotchas.html#1_14

John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Joshua D. Drake 2006-05-18 17:10:37 Re: [OT] MySQL is bad, but THIS bad?
Previous Message Josh Berkus 2006-05-18 16:38:51 Re: [OT] MySQL is bad, but THIS bad?

Browse pgsql-hackers by date

  From Date Subject
Next Message Larry Rosenman 2006-05-18 17:04:26 Re: autovacuum "connections" are hidden
Previous Message Josh Berkus 2006-05-18 16:38:51 Re: [OT] MySQL is bad, but THIS bad?