Wow, a conversation about DurationField and I totally missed it. For what it's worth, that patch needs a bit more work before even I want it included in trunk. I've been putting it off because of my file storage work, but I do plan to get back to it soon.
And Martin's right. Currently, DurationField is very much tied to dealing with all the aspects of a duration, from days to microseconds. If you need less precision, you'll pretty need to write your own. Definitely look at the existing DurationField to see how to convert to and from a Python timedelta. As for whether DurationField should be in trunk, I honestly don't have much of an opinion on the matter. It's quite possible to use it without touching trunk, so if the ticket gets marked as a wontfix, I won't cry. I'll just leave that decision to the Power That Be and see where it goes. -Gul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
