On Thu, Jun 30, 2011 at 4:51 AM, Daniel Swarbrick <daniel.swarbr...@gmail.com> wrote:
> The main difference between MySQL's "timestamp" field type and > PostgreSQL's "timestamp with time zone" field type (and indeed also > MySQL's "datetime" field type) is the date range that they support. > MySQL's "timestamp" field type is modeled on Unix epoch timestamps, > and therefore does not support dates earlier than 1 Jan, 1970 00:00:00 > UTC. PostgreSQL's "timestamp with time zone" field type on the other > hand is modeled on Julian dates, and supports dates ranging from 4713 > BC to 294276 AD (with 1 µs accuracy, I might add). And MySQL's > "datetime" field type supports some bizarre range of > '0000-00-00' (yes, you really can specify the zero'th day of the > zero'th month... isn't that cool?) to '9999-12-31'. One can only hope > that Oracle's acquisition of MySQL might one day lead to better SQL > compliance. Uh, no. 0000-00-00 is specifically an illegal value in MySQL. Invalid dates are converted to 0000-00-00 unless you are in strict mode, in which case they raise error conditions. The actual supported range is from 1000-01-01 to 9999-12-31. http://dev.mysql.com/doc/refman/5.0/en/datetime.html -- Question the answers -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
