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

Development temporary database #69

Open
allanderek opened this issue Apr 26, 2016 · 0 comments
Open

Development temporary database #69

allanderek opened this issue Apr 26, 2016 · 0 comments
Assignees

Comments

@allanderek
Copy link
Collaborator

Provide a clean way to use a temporary database whilst in development mode. The problem I have at the moment is if you make a change which requires a database migration, you don't really want to migrate the local database (or spend time writing the migration) until you're sure of the exact nature of the new database schema that you want. Hence in the meantime what you would like to do is be able to run the current state of the code with a new database. I'm typically doing this:

$ cp generated/db.sqlite current.db.sqlite

Then modify the code as much as I like and develop it, until I have the feature working. Then I can work on my new feature, get all the tests passing and such. Then develop the migration, then:

$ cp current.db.sqlite generated/db.sqlite

Check the migration and tests work and then delete the current.db.sqlite.

So basically I think I just want to codify this practice in the manage.py file.

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

1 participant