#24497: Truncation of microseconds in DateTimeField leads to lookup trouble
------------------------------+------------------------------------
Reporter: riklaunim | Owner: nobody
Type: Bug | Status: new
Component: Forms | Version: 1.7
Severity: Normal | Resolution:
Keywords: microseconds | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by riklaunim):
Replying to [comment:2 claudep]:
> It might be a use case for the `supports_microseconds` widget property
(which needs documentation, by the way).
>
> Could you try to subclass `HiddenInput`, set `supports_microseconds`
class attribute to True for your subclass, and then use that widget in
your form?
Depends what should be the default behavior for a ModelForm? Field in a
model should be tailored to a matching form field and it validation rules.
If Django must permanently modify DatetTimes for display and alike
purposes then it should be explicit and consistent with models. If form
field has supports_microseconds then maybe DateTimeField in a model should
also have such attribute so that setting timezone.now()/datetime.now()
etc. won't save with microseconds in the first place?
--
Ticket URL: <https://code.djangoproject.com/ticket/24497#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.f3b05493c22eb6257b114ea89feac9f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
