I solved a similar problem by doing the migration only for my application (manage.py makemigration my_app_name) and modifying the migration file of my app before migrate, changing the dependency value, for example assigned to 'pages', by the last pages migration created before my migration (in my case called 0003_auto_20150527_1555).
Il giorno lunedì 6 febbraio 2017 02:22:07 UTC+1, marvel tales ha scritto: > > Hello, > > I run > python manage.py makemigrations > python manage.py migrate > > I have this bug > > Apply all migrations: admin, auth, blog, conf, contenttypes, core, > django_comments, forms, galleries, generic, pages, redirects, sessions, > sites, twitter > Running migrations: > Applying blog.0003_auto_20170206_0116...Traceback (most recent call > last): > File > "/home/aa/myproject/sd_appenv/lib/python3.5/site-packages/django/db/backends/utils.py", > > line 64, in execute > return self.cursor.execute(sql, params) > psycopg2.ProgrammingError: column "title_en" of relation > "blog_blogcategory" already exists > > > The above exception was the direct cause of the following exception: > > Traceback (most recent call last): > File "manage.py", line 14, in <module> > execute_from_command_line(sys.argv) > File > "/home/aa/myproject/sd_appenv/lib/python3.5/site-packages/django/core/management/__init__.py", > > line 367, in execute_from_command_line > utility.execute() > > Thank you very much in advance > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
