From: | Lukas Smith <smith(at)pooteeweet(dot)org> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Subject: | Re: [OT] MySQL is bad, but THIS bad? |
Date: | 2006-05-18 19:58:21 |
Message-ID: | 446CD1DD.3080003@pooteeweet.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
Joshua D. Drake wrote:
> Thomas Hallgren wrote:
>> John DeSoi wrote:
>>>
>>> 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
>>>
>> Couldn't we just install something that replaced invalid dates with a
>> randomly generated but otherwise correct dates? That way they would
>> become completely invisible. No one could even tell that the date was
>> invalid to start with.
>>
>
> No we can't, because then we are taking an invalid date, which is
> potentially valid data (to the user) and modifying it to a valid date
> that is indeed invalid data.
>
> One of the reasons that mysql is just stupid.
I do agree that its probably not worth allocating core resources to
this, but spouting outdated FUD is really making you two look foolish.
You have to understand that MySQL evolves just like PostgreSQL does. So
you better focus on advertising where PostgreSQL shines instead of
poking fun at something you apparently do not follow.
regards,
Lukas
From | Date | Subject | |
---|---|---|---|
Next Message | Philippe Schmid | 2006-05-18 20:17:32 | Re: [OT] MySQL is bad, but THIS bad? |
Previous Message | Michael Paesold | 2006-05-18 19:55:52 | Re: [OT] MySQL is bad, but THIS bad? |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-05-18 20:16:56 | Re: Question about casts |
Previous Message | Michael Paesold | 2006-05-18 19:55:52 | Re: [OT] MySQL is bad, but THIS bad? |