#25154: Migration errors don't contain enough information to debug properly
------------------------------+--------------------------------------
     Reporter:  brandonmoser  |                    Owner:  nobody
         Type:  New feature   |                   Status:  new
    Component:  Migrations    |                  Version:  1.7
     Severity:  Normal        |               Resolution:
     Keywords:                |             Triage Stage:  Unreviewed
    Has patch:  0             |      Needs documentation:  0
  Needs tests:  0             |  Patch needs improvement:  0
Easy pickings:  0             |                    UI/UX:  0
------------------------------+--------------------------------------
Changes (by brandonmoser):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Old description:

> After creating a migration, via `makemigrations`, I attempted to run
> `sqlmigrate`, but received the following error. I have 3 migrations using
> the object referenced. It would be helpful to add the exact migration
> operation in the traceback. I think the migration traceback should, also,
> show the model/table and column that is part of the error.
>
> {{{
> Traceback (most recent call last):
>   File "manage.py", line 11, in <module>
>     execute_from_command_line(sys.argv)
>   File "/usr/local/lib/python2.7/dist-
> packages/django/core/management/__init__.py", line 385, in
> execute_from_command_line
>     utility.execute()
>   File "/usr/local/lib/python2.7/dist-
> packages/django/core/management/__init__.py", line 377, in execute
>     self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/usr/local/lib/python2.7/dist-
> packages/django/core/management/base.py", line 288, in run_from_argv
>     self.execute(*args, **options.__dict__)
>   File "/usr/local/lib/python2.7/dist-
> packages/django/core/management/commands/sqlmigrate.py", line 30, in
> execute
>     return super(Command, self).execute(*args, **options)
>   File "/usr/local/lib/python2.7/dist-
> packages/django/core/management/base.py", line 338, in execute
>     output = self.handle(*args, **options)
>   File "/usr/local/lib/python2.7/dist-
> packages/django/core/management/commands/sqlmigrate.py", line 61, in
> handle
>     sql_statements = executor.collect_sql(plan)
>   File "/usr/local/lib/python2.7/dist-
> packages/django/db/migrations/executor.py", line 82, in collect_sql
>     migration.apply(project_state, schema_editor, collect_sql=True)
>   File "/usr/local/lib/python2.7/dist-
> packages/django/db/migrations/migration.py", line 108, in apply
>     operation.database_forwards(self.app_label, schema_editor,
> project_state, new_state)
>   File "/usr/local/lib/python2.7/dist-
> packages/django/db/migrations/operations/fields.py", line 139, in
> database_forwards
>     schema_editor.alter_field(from_model, from_field, to_field)
>   File "/usr/local/lib/python2.7/dist-
> packages/django/db/backends/schema.py", line 460, in alter_field
>     return self._alter_many_to_many(model, old_field, new_field, strict)
>   File "/usr/local/lib/python2.7/dist-
> packages/django/db/backends/schema.py", line 764, in _alter_many_to_many
> new_field.rel.through._meta.get_field_by_name(new_field.m2m_reverse_field_name())[0],
>   File "/usr/local/lib/python2.7/dist-
> packages/django/utils/functional.py", line 17, in _curried
>     return _curried_func(*(args + moreargs), **dict(kwargs,
> **morekwargs))
>   File "/usr/local/lib/python2.7/dist-
> packages/django/db/models/fields/related.py", line 2224, in
> _get_m2m_reverse_attr
>     return getattr(self, cache_attr)
> AttributeError: 'VersionedManyToManyField' object has no attribute
> '_m2m_reverse_name_cache'
> }}}
>
> '''Note''': I have posted this error to the CleanerVersion team due to
> the exact error.

New description:

 After creating a migration, via `makemigrations`, I attempted to run
 `sqlmigrate`, but received the following error. I have 3 migrations using
 the object referenced. It would be helpful to add the exact migration
 operation in the traceback. I think the migration traceback should, also,
 show the model/table and column that is part of the error.

 {{{
 Traceback (most recent call last):
   File "manage.py", line 11, in <module>
     execute_from_command_line(sys.argv)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/__init__.py", line 385, in
 execute_from_command_line
     utility.execute()
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/__init__.py", line 377, in execute
     self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/base.py", line 288, in run_from_argv
     self.execute(*args, **options.__dict__)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/commands/sqlmigrate.py", line 30, in
 execute
     return super(Command, self).execute(*args, **options)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/base.py", line 338, in execute
     output = self.handle(*args, **options)
   File "/usr/local/lib/python2.7/dist-
 packages/django/core/management/commands/sqlmigrate.py", line 61, in
 handle
     sql_statements = executor.collect_sql(plan)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/migrations/executor.py", line 82, in collect_sql
     migration.apply(project_state, schema_editor, collect_sql=True)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/migrations/migration.py", line 108, in apply
     operation.database_forwards(self.app_label, schema_editor,
 project_state, new_state)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/migrations/operations/fields.py", line 139, in
 database_forwards
     schema_editor.alter_field(from_model, from_field, to_field)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/backends/schema.py", line 460, in alter_field
     return self._alter_many_to_many(model, old_field, new_field, strict)
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/backends/schema.py", line 764, in _alter_many_to_many
 
new_field.rel.through._meta.get_field_by_name(new_field.m2m_reverse_field_name())[0],
   File "/usr/local/lib/python2.7/dist-
 packages/django/utils/functional.py", line 17, in _curried
     return _curried_func(*(args + moreargs), **dict(kwargs, **morekwargs))
   File "/usr/local/lib/python2.7/dist-
 packages/django/db/models/fields/related.py", line 2224, in
 _get_m2m_reverse_attr
     return getattr(self, cache_attr)
 AttributeError: 'VersionedManyToManyField' object has no attribute
 '_m2m_reverse_name_cache'
 }}}

 '''Note''': The issue with the VersionedManyToManyField has a reported
 issue with the CleanerVersion team and can be found
 [https://github.com/swisscom/cleanerversion/issues/56 (here)].

--

--
Ticket URL: <https://code.djangoproject.com/ticket/25154#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.3a17ccd6ef1e03a6b276808ce1ac1b44%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to