Wiadomość napisana w dniu 2009-12-02, o godz. 11:30, przez chefsmart:
> Hi, I'm am getting MySQL error 1406 while running syncdb. (See link
> http://pastebin.org/59605)
>
> This happens after I create the superuser.
>
> The error says _mysql_exceptions.DataError: (1406, "Data too long for
> column 'name' at row 1")
>
> I am not doing any pre-population of data. So I checked the tables
> whose names start with "django_" and columns called "name" appear for
> the django_content_type table and the django_site tables. The former
> is varchar(100) and the latter is varchar(50).
>
> I am definitely safe as far as the django_site table is concerned. And
> I am also safe with the django_content_type table so I'm not sure why
> this is happening.
>
> Where does Django populate the django_content_type.name column from? I
> am guessing it would take the model name or the verbose_name if
> supplied.
>
> All my models are named well within the varchar(100) limit.
>
> Any idea what is going on? By the way, I'm also using contrib.auth.
Here's the culprit:
File "D:\Python25\lib\site-packages\django\contrib\auth\management
\__init__.py", line 28, in create_permissions defaults={'name': name,
'content_type': ctype})
Do you have any custom-defined permissions for your models?
--
Artificial intelligence stands no chance against natural stupidity
Jarek Zgoda, R&D, Redefine
jarek.zg...@redefine.pl
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@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.
