Re: [OT] MySQL is bad, but THIS bad?
От | Joshua D. Drake |
---|---|
Тема | Re: [OT] MySQL is bad, but THIS bad? |
Дата | |
Msg-id | 446CCFD3.4090105@commandprompt.com обсуждение исходный текст |
Ответ на | Re: [OT] MySQL is bad, but THIS bad? (Thomas Hallgren <thomas@tada.se>) |
Ответы |
Re: [OT] MySQL is bad, but THIS bad?
Re: [OT] MySQL is bad, but THIS bad? |
Список | 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@postgresql.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 solutionssince 1997 http://www.commandprompt.com/
В списке pgsql-hackers по дате отправления: