| From: | Michael Paesold <mpaesold(at)gmx(dot)at> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Thomas Hallgren <thomas(at)tada(dot)se>, 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:55:52 |
| Message-ID: | 446CD148.5040709@gmx.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Joshua D. Drake wrote:
> Thomas Hallgren wrote:
>
>> 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.
I think you should have read a `;-)' after Thomas' suggestion.
;-)
Best Regards,
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Smith | 2006-05-18 19:58:21 | Re: [OT] MySQL is bad, but THIS bad? |
| Previous Message | Joshua D. Drake | 2006-05-18 19:49:39 | Re: [OT] MySQL is bad, but THIS bad? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Smith | 2006-05-18 19:58:21 | Re: [OT] MySQL is bad, but THIS bad? |
| Previous Message | Joshua D. Drake | 2006-05-18 19:49:39 | Re: [OT] MySQL is bad, but THIS bad? |