#14820: Use `TextField` instead of `PositiveIntegerField` in docs and examples
for
generic relations.
-----------------------------------------+----------------------------------
Reporter: mrmachine | Owner:
Status: new | Milestone: 1.3
Component: Documentation | Version: SVN
Resolution: | Keywords: generic relation
genericforeignkey object_id type textfield sprintdec2010
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
-----------------------------------------+----------------------------------
Comment (by gabrielhurley):
My bigger concern goes back to the fact that what goes into this section
of the docs becomes a sort of "official recommendation". `TextField` is
off the table, and I don't mind `CharField`, but Paul's concern about
having to choose a length for a `CharField` is a valid one, and I don't
have an answer there. What's the right compromise between "generic" and
performant here?
--
Ticket URL: <http://code.djangoproject.com/ticket/14820#comment:14>
Django <http://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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
