exception messages: What does it mean? - django 1.8 python 3.4 - python manage.py makemigrate -
this error message: not sure exception message mean. plus don't seem error while running local server. going throw error in future?
(proj1) c:\users\vetri\google drive\proj1\src>python manage.py mak emigrations no changes detected (proj1) c:\users\vetri\google drive\proj1\src>python manage.py mig rate operations perform: synchronize unmigrated apps: messages, staticfiles apply migrations: contenttypes, sessions, admin, index, auth synchronizing apps without migrations: creating tables... running deferred sql... installing custom sql... running migrations: rendering model states... done applying index.0001_initial...traceback (most recent call last): file "c:\users\vetri\google drive\proj1\lib\site-packages\django\db\bac kends\utils.py", line 62, in execute return self.cursor.execute(sql) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\db\bac kends\sqlite3\base.py", line 316, in execute return database.cursor.execute(self, query) sqlite3.operationalerror: table "index_usermanagement" exists above exception direct cause of following exception: traceback (most recent call last): file "manage.py", line 10, in <module> execute_from_command_line(sys.argv) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\core\m anagement\__init__.py", line 338, in execute_from_command_line utility.execute() file "c:\users\vetri\google drive\proj1\lib\site-packages\django\core\m anagement\__init__.py", line 330, in execute self.fetch_command(subcommand).run_from_argv(self.argv) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\core\m anagement\base.py", line 390, in run_from_argv self.execute(*args, **cmd_options) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\core\m anagement\base.py", line 441, in execute output = self.handle(*args, **options) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\core\m anagement\commands\migrate.py", line 221, in handle executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\db\mig rations\executor.py", line 110, in migrate self.apply_migration(states[migration], migration, fake=fake, fake_initial=f ake_initial) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\db\mig rations\executor.py", line 147, in apply_migration state = migration.apply(state, schema_editor) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\db\mig rations\migration.py", line 115, in apply operation.database_forwards(self.app_label, schema_editor, old_state, projec t_state) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\db\mig rations\operations\models.py", line 59, in database_forwards schema_editor.create_model(model) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\db\bac kends\base\schema.py", line 286, in create_model self.execute(sql, params or none) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\db\bac kends\base\schema.py", line 111, in execute cursor.execute(sql, params) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\db\bac kends\utils.py", line 79, in execute return super(cursordebugwrapper, self).execute(sql, params) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\db\bac kends\utils.py", line 64, in execute return self.cursor.execute(sql, params) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\db\uti ls.py", line 97, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\utils\ six.py", line 658, in reraise raise value.with_traceback(tb) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\db\bac kends\utils.py", line 62, in execute return self.cursor.execute(sql) file "c:\users\vetri\google drive\proj1\lib\site-packages\django\db\bac kends\sqlite3\base.py", line 316, in execute return database.cursor.execute(self, query) django.db.utils.operationalerror: table "index_usermanagement" exists (proj1) c:\users\vetri\google drive\proj1\src>
you must have run syncdb before doing migrations or anothee possible reason using other version of database have table try remove table 'index_usermanagement' exists! after again run
python manage.py migrate
Comments
Post a Comment