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?
J. Leclanche / Adys 2010/1/21 Łukasz Rekucki <lreku...@gmail.com>: > Hi, if i'm wrong, please ignore this post ;) > > 2010/1/21 Jerome Leclanche <adys...@gmail.com>: >> A decimal backend was a lot worse than a bigint backend on that matter >> (slower, made a lot less sense as well). >> >> 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. > > I did a little searching and I found that: > > * Oracle implements SQL92's INTERVAL DAY TO SECOND > * Mysql has TIME > * PostreSQL has of course the INTERVAL > * SQLite3 doesn't support any kind of time fields (datetime, time, > interval), but accepts all as legal types. > > So actually, all django backends support some kind of INTERVAL field. > To be clear, I'm not criticizing your approach with BigInt, nor I have > time & enough django expertise to provide a patch for this using > native datatypes. > > Best regards, > Lukasz 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. > > > >
-- 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.
