Did you have unique=True when you created the database with south? If not,
I cannot any reason for the discrepancy you are describing. south does
treat apps that have migrations separately from the rest, but that doesn't
seem to be related to the issue you had.
On Tuesday, November 19, 2013 7:5
Thanks for tip tim.
Actually I have noticed a weird thing. Hope you can explain why it happened:
Initially, I had installed south. when I created a fresh sqlite database,
the module that I created always came separate form others. That is
.manage.py syncdb resulted in
Not synced (use migrations
If you first run syncdb with the UserPic.user field unique=True, it's not
enough just to change unique=False. You'll also need to remove the database
unique constraint. Do you have the problem on a fresh syncdb if
unique=False? If so, it would be helpful to include the full traceback of
the err
I'm Django noob so please bear with me. I am trying to make a simple
gallery for usres so that they can upload pics to their profile. Here are
the relevant parts:
models.py
def get_uplaod_file_name(instance,filename):
return 'uploaded_files/%s_%s' % (str(time()).replace('.','_'), filenam
4 matches
Mail list logo
