Changes between Initial Version and Version 1 of Ticket #9190


Ignore:
Timestamp:
09/23/08 17:09:37 (6 years ago)
Author:
kmtracey
Comment:

It isn't necessary to run sql (which actually does nothing with the database, it just prints out statements for your information) or syncdb after adding a __unicode__() method to a model. Syncdb creates tables, you only need to run it when you add a model to your application. I am not sure what you mean by "upload the model" as the word "upload" doesn't appear on the page you pointed to. I'm not really sure what happened in your case that was fixed by running syncdb, but telling people to re-run it after adding the __unicode__() method is not correct.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9190

    • Property Status changed from new to closed
    • Property Patch needs improvement unset
    • Property Needs tests unset
    • Property Needs documentation unset
    • Property Resolution changed from to invalid
  • Ticket #9190 – Description

    initial v1  
    1 At http://docs.djangoproject.com/en/dev/intro/tutorial01/#intro-tutorial01 it doesn't tell you that you have to use the sql and syncdb commands again after you add the __unicode__() method to the model and upload the model. I figured that out by trial and error; the documentation should be more explicit.
     1At http://docs.djangoproject.com/en/dev/intro/tutorial01/#intro-tutorial01 it doesn't tell you that you have to use the sql and syncdb commands again after you add the `__unicode__()` method to the model and upload the model. I figured that out by trial and error; the documentation should be more explicit.
Back to Top