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

installation guide - can't upgrade existing databases #754

Closed
ahmadia opened this issue Nov 3, 2015 · 6 comments
Closed

installation guide - can't upgrade existing databases #754

ahmadia opened this issue Nov 3, 2015 · 6 comments
Milestone

Comments

@ahmadia
Copy link
Contributor

ahmadia commented Nov 3, 2015

Instruct users to manually remove db.sqlite3 if installing from an older version of Memex Explorer, as migrations are not supported.

@ahmadia ahmadia added this to the v0.4 milestone Nov 3, 2015
@brittainhard
Copy link
Contributor

I think we can fix this by tracking migrations beyond 0001. I'll look into it later.

@brittainhard
Copy link
Contributor

@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.

@ahmadia
Copy link
Contributor Author

ahmadia commented Nov 5, 2015

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?

@brittainhard
Copy link
Contributor

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.

@ahmadia
Copy link
Contributor Author

ahmadia commented Nov 5, 2015

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.

@brittainhard
Copy link
Contributor

Fair enough. I'll add this in a PR.

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

No branches or pull requests

2 participants