Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do app not migrating #109

Open
dpiaquadio opened this issue May 3, 2013 · 4 comments
Open

Do app not migrating #109

dpiaquadio opened this issue May 3, 2013 · 4 comments

Comments

@dpiaquadio
Copy link
Member

After running setup_db.py, I tried to migrate all the apps that weren't synced. I couldn't do it because this error was raised:
"ValueError: Cannot import the required field 'utility.models.GenericPartyForeignKey'."

Is it possible that the migrate is looking for the app in the wrong spot (ie: not searching in what_apps)?

@jMyles
Copy link
Member

jMyles commented May 3, 2013

Can you paste a complete traceback?

@dpiaquadio
Copy link
Member Author

After typing python manage.py migrate do, this is the traceback:

/home/dominick/virtualenv/WHAT/local/lib/python2.7/site-packages/django/utils/hashcompat.py:9: DeprecationWarning: django.utils.hashcompat is deprecated; use hashlib instead
DeprecationWarning)

/home/dominick/virtualenv/WHAT/local/lib/python2.7/site-packages/django/contrib/localflavor/init.py:2: DeprecationWarning: django.contrib.localflavor is deprecated. Use the separate django-localflavor-* packages instead.
warnings.warn("django.contrib.localflavor is deprecated. Use the separate django-localflavor-* packages instead.", DeprecationWarning)

Running migrations for do:

  • Migrating forwards to 0002_auto__add_field_task_status.

    do:0001_initial
    ValueError: Cannot import the required field 'utility.models.GenericPartyForeignKey'

@dpiaquadio
Copy link
Member Author

Should this not be importing 'what_apps.utility.models.GenericPartyForeignKey'? If so, where can I find the code to do so?

@jMyles
Copy link
Member

jMyles commented May 8, 2013

Gotcha. OK, my take:

  1. What is the standard practice if you have a migration that is from before a refactor, as we have here?
  2. Sure, you can change it if you want in do.migrations.0002 or whatever.
  3. We're never, ever going to rollback this migration - I'm not opposed to deleting it at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants