#14094: Cannot define CharField with unlimited length
------------------------------+------------------------------------
Reporter: millerdev | Owner: nobody
Type: New feature | Status: reopened
Component: Core (Other) | Version: 1.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Changes (by jacob):
* stage: Design decision needed => Accepted
Comment:
We should do this. Postgres, at least, has no performance or storage space
penalty for using `varchar` over `varchar(n)` -- the length requirement is
basically a constraint, that's all. I imagine other modern DBs are
similar, but even if not it's still a good idea to let users make the
call, not do it unilaterally.
--
Ticket URL: <https://code.djangoproject.com/ticket/14094#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 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 https://groups.google.com/groups/opt_out.
