2010/1/21 Jerome Leclanche <adys...@gmail.com>: > Hi Lukasz, thanks for the wrap up > > 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?
>From my understanding of the docs PostgreSQL can do microseconds (6digits), Oracle - nanoseconds (9digits), SQLite3 seems to accept miliseconds in string representation "HH:MM:SS.SSS". And the worst case is MySQL: """A trailing .uuuuuu microseconds part of TIME values is allowed under the same conditions as for other temporal values, as described in Section 10.3.1, “The DATETIME, DATE, and TIMESTAMP Types”. This includes the property that any microseconds part is discarded from values stored into TIME columns.""" After seeing all this mess, i'm +1 on using BigIntField. Good work. -- Łukasz Rekucki
-- 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.
