#25556: Add DatePart db expression to allow complex lookups on date parts (e.g.
year, month, day)
-------------------------------------+-------------------------------------
Reporter: ryuusenshi | Owner:
| ryuusenshi
Type: New feature | Status: assigned
Component: Database layer | Version: 1.9a1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: db expressions | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by akaariai):
I don't mind the renaming. The pre-release period is for polishing new
implementations.
I guess I withdraw my objection about 1.9. We are doing two things here:
1. Changing some names. We are going to do this no matter if we add
documentation for this.
2. Adding the date expressions as a new feature by documenting existing
code.
Doing 2. alone doesn't seem too bad. We aren't doing any code changes for
the feature. So, I don't object, but I still think we should be extremely
careful in not making the feature freeze a debatable issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/25556#comment:7>
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/068.3a6f24a8334da2c558dc88047e950f0d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
