#16187: Refactor lookup system
-------------------------------------+-------------------------------------
Reporter: UloPe | Owner: UloPe
Type: | Status: new
Cleanup/optimization | Component: Database layer
Milestone: | (models, ORM)
Version: 1.3 | Severity: Normal
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by UloPe):
* owner: nobody => UloPe
* needs_better_patch: 0 => 1
* has_patch: 0 => 1
Comment:
The t16187-proof-of-concept patch - as the name says - is a (quick and
dirty) proof of concept (the testsuite passes, including those tests in
tests-t16187-2.patch)
This means that fields may be named like lookup types and new lookup types
can be added at will without backwards compatibility concerns.
This patch definitely needs improvement / cleanup before its RFC.
--
Ticket URL: <https://code.djangoproject.com/ticket/16187#comment:3>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
