On Sep 14, 2008, at 4:22 PM, sal wrote: > > Have looked extensively but cannot find a solution :( > > While trying to follow tutorial in a django book, I get the following > error when running manage.py a second time: > > _mysql_exceptions.OperationalError: (1050, "Table 'people_person' > already exists > ") > > I am running a development server on Windows with Mysql 5, Python25, > django, MySQL-python.exe-1.2.1_p2.win32-py2.5.exe > > I have added 'uses_case_insensitive_names = True' inside: > C:\Python25\Lib\site-packages\django\db\backends\__init__.py > > The error is fixed if i change the case of the models name to match > the database table in models.py but I think this is the correct > solution. > > Would appreciate any advice, thanks.
What you are doing is most certainly not the correct solution, because you are changing the DB backend, telling it to treat MySQL as case- insensitive. This is wrong. MySQL table names are case sensitive when MySQL is running on case-sensitive filesystems such as Unix/Linux/some OSX. What you changed is a core Django variable, not an end-user setting. It is there because the back-end is written to deal with MySQL in a case-sensitive manner, which will also work on a case-insensitive filesystems. The correct solution is what you did: match case, because that is what the MySQL backend requires. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
