On 23-8-2012 4:53, Mhlanga Bothin wrote:
>
> On 23/08/2012, at 10:59 AM, Melvyn Sopacua wrote:
>
>> On 23-8-2012 2:37, Mhlanga Bothin wrote:
>>
>>> Thanks a lot for your help. I am not adding any classes to the app on
>>> the second sync, correct me if I am wrong but django only resyncs new
>>> classes?
>>
>> Yes and no. The permissions are a special case, they are also updated if
>> you add permissions to a model's Meta class. Is there any difference at
>> all between the first and second sync? Or can you reproduce this with an
>> entirely empty database and just run syncdb twice in a row?
>>
>> --
>> Melvyn Sopacua
>
>
> Thanks. There is no difference between the first sync and the second sync.
>
> Procedure:
>
> Drop data base
> Create new data base
> syncdb
> syncdb: Error
>
> :(
>
> Is there any other debug output that I can look through?
Well, the only difference between a pristine run and the one following
is that the superuser doesn't exist. But probably the attached patch can
show you what's going on.
--
Melvyn Sopacua
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
diff -r d34ef21d60a1 django/contrib/auth/management/__init__.py
--- a/django/contrib/auth/management/__init__.py Fri Aug 17 17:07:54
2012 +0200
+++ b/django/contrib/auth/management/__init__.py Fri Aug 24 01:47:35
2012 +0200
@@ -28,6 +28,10 @@
from django.contrib.contenttypes.models import ContentType
app_models = get_models(app)
+ if verbosity :
+ self.stderr.write(
+ 'Models for {}: {}'.format(app, app_models)
+ )
# This will hold the permissions we're looking for as
# (content_type, (codename, name))
