New issue 114 by ad...@jfsimon.fr: Django Evolution doesn't convert
ForeignKey to OneToOneField
http://code.google.com/p/django-evolution/issues/detail?id=114
What steps will reproduce the problem?
1. Turn a ForeignKey to OneToOneField
2. Execute ./manage evolve --hint --execute
Expected : Are you sure you want to execute the evolutions?
Seen : Following Traceback
Version : Revision 166
Database : Postgresql
Traceback (most recent call last):
File "manage.py", line 13, in <module>
execute_manager(settings)
File
"/usr/lib/python2.6/dist-packages/django/core/management/__init__.py", line
438, in execute_manager
utility.execute()
File
"/usr/lib/python2.6/dist-packages/django/core/management/__init__.py", line
379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python2.6/dist-packages/django/core/management/base.py",
line 195, in run_from_argv
self.execute(*args, **options.__dict__)
File "/usr/lib/python2.6/dist-packages/django/core/management/base.py",
line 222, in execute
output = self.handle(*args, **options)
File
"/usr/lib/python2.6/dist-packages/django_evolution/management/commands/evolve.py",
line 87, in handle
hinted_evolution = diff.evolution()
File "/usr/lib/python2.6/dist-packages/django_evolution/diff.py", line
197, in evolution
changed_attrs[prop] = current_field_sig.get(prop,
ATTRIBUTE_DEFAULTS[prop])
KeyError: 'field_type'
I'd like to say that Django-Evolution is REALLY helpful !
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings