Code

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#7523 closed (invalid)

The max_length needs to become maxlength

Reported by: anonymous Owned by: nobody
Component: Documentation Version: master
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

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.

Attachments (0)

Change History (2)

comment:1 Changed 6 years ago by Simon Greenhill

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

No, maxlength is deprecated. max_length is the key to use. See e.g. #2101

comment:2 Changed 6 years ago by ubernostrum

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.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.