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

Migrations Outdated #7

Closed
AstraLuma opened this issue Mar 10, 2016 · 4 comments
Closed

Migrations Outdated #7

AstraLuma opened this issue Mar 10, 2016 · 4 comments

Comments

@AstraLuma
Copy link
Contributor

The migrations have unsynced changes.

@adamalton
Copy link
Owner

I can't see a difference between the model definition and the model that would be created by the migration files (although I'm only reading the code on GitHub, not running it). What's missing?

This isn't just because you haven't yet run the migrations is it?

@AstraLuma
Copy link
Contributor Author

Ah, that's it.

I think it's generally traditionally to package and version migrations with your app, so that when an a user updates their copy, Django knows what incremental database changes need to be made.

@adamalton
Copy link
Owner

Ah good, I didn't think the migrations were wrong.

I haven't got around to doing a release to PyPi yet. I'm on holiday at the moment, but will endeavour to do it when I'm back.

@adamalton
Copy link
Owner

I've made a separate issue to do a release to PyPi (#9).

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