Hi, I'm new to Django so excuse me if it's a noob question.

I have a Django app, let's call it "project", that uses a Django reusable 
app, let's call it "app", version controlled on github, and tagged.

1. I create a first version of the app with its initial 0001_initial.py 
migration file, tag it 0.0.1, and add it to "project" requirements.txt
2. I then run "python manage.py migrate app". This picks 0001_initial and 
applies the migration.
3. I do changes to app, add a field, I have 0002_model_newfield.py file, I 
tag it 0.0.2, and change the version required in requirements.txt
4. I run "python manage.py migrate app". This picks 0002_model_newfield and 
applies the migration.

Now, what happens if I want to go back to version "0.0.1" of the app? I can 
change the requirements, reinstall the library, but migrate won't do much 
if I go back to a state where I have less migration files available.
The only thing I can do, I think, is stay on "0.0.2", do a "python 
manage.py migrate app 0001", and then switch back to the "0.0.1" version.

I haven't found any information on how you version control alongside with 
git and downgrade django reusable apps. Maybe there is an open source 
project that can provide some pointers?

I'm just starting with this and I might have more complex dependencies to 
deal with, I just want to make sure I'm not missing something obvious here.

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/e7a1404d-bb4a-401d-bdc2-9d7de1ad8e71%40googlegroups.com.

Reply via email to