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

Already on GitHub? Sign in to your account

Fixes for initial migration issues #17

Merged
merged 2 commits into from Feb 11, 2012

Conversation

Projects
None yet
3 participants
Contributor

zerok commented Feb 6, 2012

Right now when starting a new project with cab the initial migrations fail due to missing fixtures (like Python as a Language) and missing content types (which are probably created after the initial migrations have been completed).

This patch skips the content migration for Python snippets if no such language is available and also disables the content type migration if the relevant content types don't exist yet.

@jezdez jezdez and 1 other commented on an outdated diff Feb 8, 2012

cab/migrations/0005_populate_version.py
@@ -5,11 +5,16 @@
from django.db import models
from cab.models import VERSION_MAPPING
+import cab.models
@jezdez

jezdez Feb 8, 2012

Owner

What's this import for?

@zerok

zerok Feb 8, 2012

Contributor

Ah, sorry. This was a remnant of testing some other exceptions.

Contributor

coleifer commented Feb 8, 2012

Nice! Thanks for looking into this one

@zerok zerok added a commit that referenced this pull request Feb 11, 2012

@zerok zerok Merge pull request #17 from zerok/initial-setup-migrations
Fixes for initial migration issues
8887ade

@zerok zerok merged commit 8887ade into django:master Feb 11, 2012

Contributor

zerok commented Feb 11, 2012

Got no negative feedback about this anymore, so the merge is now complete ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment