#7523 closed (invalid)
The max_length needs to become maxlength
| Reported by: | anonymous | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
In de documentation overview, the creation of a model is shown. But a small typo crept in:
The varchar length can not be set using max_length, but by using maxlength.
Change History (2)
comment:1 by , 16 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 16 years ago
Simon, most likely this was someone trying to do the tutorial for the development version (where max_length is correct) while using the Django 0.96 codebase (where max_length is incorrect). We get these every so often, and point people to the big warning at the top of each documentation page outlining which version of Django it's written for.
Note:
See TracTickets
for help on using tickets.
No, maxlength is deprecated. max_length is the key to use. See e.g. #2101