-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/31/07 16:50, Joshua J. Kugler wrote: > On Wednesday 31 January 2007 13:19, Roberto C. Sanchez wrote: >>> How do I get started here? >> First. Please do not use MySQL, unless you don't care about your data. > > Please stop this MySQL vs. PostgreSQL bashing. Each has their place. If > users of MySQL don't care about their data, then I guess Bayer, Colgate, > Ensembl Genome Browser, Genome Sciences Center (GSC), The Institute for [snip] > Feedster, Flickr, Freshmeat.net, Technorati, Wikipedia, and YouTube (among > many others, see http://www.mysql.com/customers/ ) don't care about their > data. These are companies that live and die by their data, I'm sure they > care about it very much. Each has their place. MySQL has come a long way > since its 3.23 days. Read the manual. Form your own opinions. A lot has > changed.
I supplied a link to the official MySQL docs. I'll quote from them now, if you'd like: http://dev.mysql.com/doc/refman/5.0/en/constraint-invalid-data.html MySQL allows you to store certain incorrect date values into DATE and DATETIME columns (such as '2000-02-31' or '2000-02-00'). The idea is that it's not the job of the SQL server to validate dates. If MySQL can store a date value and retrieve exactly the same value, MySQL stores it as given. If the date is totally wrong (outside the server's ability to store it), the special ?zero? date value '0000-00-00' is stored in the column instead. So, I'd say that yes, anyone who specs MySQL either (a) does not know WTF they are doing, or (b) cares more about MySQL's supposed raw speed than about the validity of their data. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFwSQrS9HxQb37XmcRAqO4AJ9KS32CXUT+DBWr1pH0RcjvfpmnJQCeM8nI pU2ZJ+HYHutmFq3uhQwR/Fo= =R7GI -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
