From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Thomas Hallgren <thomas(at)tada(dot)se> |
Cc: | John DeSoi <desoi(at)pgedit(dot)com>, 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 19:49:39 |
Message-ID: | 446CCFD3.4090105@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
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.
Joshua D. Drake
> Regards,
> Thomas Hallgren
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paesold | 2006-05-18 19:55:52 | Re: [OT] MySQL is bad, but THIS bad? |
Previous Message | Jim C. Nasby | 2006-05-18 19:43:23 | Re: [OT] MySQL is bad, but THIS bad? |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paesold | 2006-05-18 19:55:52 | Re: [OT] MySQL is bad, but THIS bad? |
Previous Message | Jim C. Nasby | 2006-05-18 19:43:23 | Re: [OT] MySQL is bad, but THIS bad? |