Opened 7 years ago

Closed 7 years ago

#5653 closed (invalid)

unicode in tutorial documentation

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


Unless I am mistaken, python syncdb should be run after changes to

If so, please consider clarifying the tutorial documentation in the section that discusses adding unicode to the polls and choice models. Up until that point, django newbies following the tutorial literally will get dropped because they will not see the prescribed change. When they don't, the documentation faults a code version issue when it might be more likely that they simply didn't sync their new model after they changed it?

Attachments (0)

Change History (1)

comment:1 Changed 7 years ago by ubernostrum

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

syncdb, per its reference documentation, only creates tables which have not yet been created. It does not make modifications -- that is, it never issues ALTER TABLE statements. And simply adding a method to a model does not require a database-level change, because it does not change the schema of the table for that model (in fact, nothing in the tutorial makes a change to the DB schema once the initial table for each model is created); adding the __unicode__ method, then, works fine without doing anything else.

Add Comment

Modify Ticket

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

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

Note: See TracTickets for help on using tickets.