#20546: New model – ApproximateDateField
-------------------------------------+-------------------------------------
Reporter: vericule@… | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.5
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aastrand):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Hello,
I have the same use case in my genealogy project. I have various
information for example for the birthday of my individuals like "Dec
1708", "Est.(imated to) 1706", "14 Jan 1708", "1702", etc. where I for
example want the persons properly ordered according to the birthday and
different kinds of filtering. I handle that in my views, and I would
assume there are quite few us that have a "not-so-elegant" and a "not-
very-efficient" model for handling similar use cases. I would prefer to
call it FlexibleDateField (in contrast to the python DateField that is in
Django), but I would also assume that the meaning of flexibility would
vary from user to user. Still, it is not possible to extend the present
DateField; one has to start from scratch so there should be some common
denominator.
--
Ticket URL: <https://code.djangoproject.com/ticket/20546#comment:1>
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/078.03b47fb612d195308064f44b5d64c98a%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
