On 01/21/2010 12:14 AM, Jerome Leclanche wrote: > Keep in mind, TIME fields are for storing time, not for storing > durations. For durations, postgres has an INTERVAL field (cf ticket), > however not every database has that field type.
Not in MySQL, from the official docs: "TIME values may range from '-838:59:59' to '838:59:59'. The hours part may be so large because the TIME type can be used not only to represent a time of day (which must be less than 24 hours), but also elapsed time or a time interval between two events (which may be much greater than 24 hours, or even negative)." SQLite3 also doesn't complain when setting a time column to eg '900:00:00'. So for consistence with the database, I'd say that either TIME or INTERVAL (for postgres) can be used. No need for integers so far. -- Olivier
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
