On Wed, Mar 25, 2009 at 5:39 PM, Darren Mansell <darren.mans...@gmail.com>wrote:
> I'm just trying to do a bit of home development on Ubuntu 9.04 which has > Python 2.6. > > When trying to populate the database from the models it's randomly ignoring > model definitions. I have no idea what's going on but the deprecation > warning of sets may be to do with it? > Unlikely. A deprecation warning is just a signal that the referenced module will be going away, so the code using it should be changed to use the replacement, but it is still functional. (This particular DeprecationWarning is coming from the MySQLdb code, not Django itself.) I cannot recreate what you are reporting with Python 2.6 and MySQL backend, only on Windows in my case, since I don't have Ubuntu 9.04. I get, on a fresh DB: D:\u\kmt\software\web\playground>manage.py syncdb D:\bin\Python2.6\lib\site-packages\MySQLdb\__init__.py:34: DeprecationWarning: the sets module is deprecated from sets import ImmutableSet Creating table auth_permission Creating table auth_group Creating table auth_user Creating table auth_message Creating table django_content_type Creating table django_session Creating table django_site Creating table bmi_servertype Creating table bmi_tomcatstyle Creating table bmi_server Creating table bmi_site Creating table bmi_buildtype Creating table bmi_buildstage Creating table bmi_build Creating table bmi_deployto Creating table bmi_generalsettings Creating table django_admin_log You just installed Django's auth system, which means you don't have any superusers defined. Would you like to create one now? (yes/no): no Installing index for auth.Permission model Installing index for auth.Message model Installing index for bmi.Server model Installing index for bmi.Site model Installing index for bmi.Build model Installing index for bmi.DeployTo model Installing index for admin.LogEntry model which looks to have all the models defined in your models.py file. You say 'randomly' above -- do you mean to say if you run syncdb multiple times different models are not created each time? If you are runnnig syncdb multiple times, are you sure you have dropped all the bmi_ tables in between? The only time I've seen syncdb not create a table for a model is when the table already exists in the DB. Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---