-
Notifications
You must be signed in to change notification settings - Fork 69
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
installation guide - can't upgrade existing databases #754
Comments
I think we can fix this by tracking migrations beyond 0001. I'll look into it later. |
@ahmadia i think for this all we have to is just start tracking migration scripts beyond 0001. It wouldnt be necessary to add it to the docs, I don't think. |
Do you want to go through and generate migration scripts for the previous releases or do you want to just start allowing migration from 0.4? |
Grandfathering in migrations seems like a huge headache. I think we should just change this behavior going forward. All that is necessary is to change the .gitignore file to allow tracking migrations. We may encounter problems if we are both modifying the Django models, but I feel like we can deal with those issues when they come up. |
That's fine, I'll let you handle migrations. We still need a note in the documents for people coming from a pre-0.4 release, since we don't promise migrations up to 0.4. |
Fair enough. I'll add this in a PR. |
Instruct users to manually remove
db.sqlite3
if installing from an older version of Memex Explorer, as migrations are not supported.The text was updated successfully, but these errors were encountered: