Hi again,
I really don't understand why you need to downgrade anything? If you are running your app with an old version of the code that isn't migrated - just work on that code (you have the code tagged and stored in a git repository I hope?). When you are working on an older codebase - you will need to just create a database that corresponds to your code (by migrating to that version from an empty database).
Upgrading the database would be done via the standard migrations.
I don't know how to revert migrations though - I do think it's possible....
Med vänliga hälsningar,
Andréas
2018-08-04 17:49 GMT+02:00 HEMENDRA SINGH HADA <hada.hemendra90@gmail.com>:
Sorry for making requirement complex. My requirement is like I have released first version of my app. After that we have change some table attribute and also added some new tables in my app DB(sqlite). In this sitution I need both side compatibility(Downgrade and upgrade) for my application.--On Sat, Aug 4, 2018 at 8:59 PM Andréas Kühne <andreas.kuhne@hypercode.se> wrote:To view this discussion on the web visit https://groups.google.com/d/Hi,--I don't really understand your requirements here. If you take a backup you will get the database exactly how the database is now. If you have made any changes to the database layout, you would be able to run migrations again to upgrade the database to the latest again. For this you can use the standard migrations in Django.The database stores the level of migrations the database has been migrated to - so you can reload a backup at any stage.Regards,Andréas2018-08-04 16:23 GMT+02:00 HEMENDRA SINGH HADA <hada.hemendra90@gmail.com>:I have a django based application. In this we are providing backup and restore facility for user. DB which we are using is sqlite. So please suggest me how to migrate database accordingly - both downgrade and upgrade for sqlite.--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com .
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users .
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/c103056c- .a8e5-410d-adb3-b0d9bc5d1ac5% 40googlegroups.com
For more options, visit https://groups.google.com/d/optout .
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com .
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users .msgid/django-users/ .CAK4qSCcPJ15gtsDmptp5vv4j4%3D_ Q7CLDJq1Z5S5eUv1pqLrcow% 40mail.gmail.com
For more options, visit https://groups.google.com/d/optout .
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com .
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users .
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CACgU_ .Vj7LqC0Q2Gs7DrwY%3D62% 3DySmJkiKE4TTGmptP3K1Q%3DOrkQ% 40mail.gmail.com
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAK4qSCd1UVyUze1m%3DDaRhSsqkgcyX8xONyPydVPt0C5JsmG8%3DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment