Which is exactly what I'm doing using a BigIntegerField...
J. Leclanche / Adys



On Thu, Jan 21, 2010 at 1:57 AM, Olivier Guilyardi <m...@xung.org> wrote:
> On 01/21/2010 12:44 AM, Jerome Leclanche wrote:
>>
>> Main issue is precision. I personally very, very often work with
>> milliseconds, and I can imagine many use cases where I'd need to work
>> with microseconds. How many of these backends do not at least support
>> millisecond precision?
>
> If you want to go that way then you should also modify TimeField to support 
> such
> precision.
>
> IMO precision can be dealt with by using a numeric field explicitly.
>
> --
>  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.
>
>
>
>
-- 
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.


Reply via email to