I have a django project with an existing db that I would really like to avoid dumping or interrupting. I am attempting to install South but when I run my initial migration python manage.py migrate exa
So, I\'ve my application stack and I\'m ready to deploy it to my webserver. I\'m deploying to a fresh, clean and bla开发者_运维技巧nk database, so what command to I run?Do I run ./manage.py syncdb or
I have a Django project using South that includes an install script. What I\'d like to do is have a couple of lines of code in that install script that take care of installing and syncing my database
I was doing some system and my table design was like this: Table A: - ID - ForeignKey(C) Table B: - ID - ForeignKey(A)
I installed SOUTH and migrated 开发者_C百科few apps. now i want to go back to syncDB and uninstall SOUTH.
I am using South to change a ForeignKey TO ManyToManyField in one of the models in Django but it is not working out as expected.
I used South as the migration tool, but i dint know开发者_如何学C it will format all my db ! I dont want to lose my db . It doesn\'t have to format your data, you can integrate existing apps/tables:
I want to add a ForeignKey field to my model. In order to achieve that, I did 3 steps: Added the ForeignKey field with null=True to my model, and then created a schemamigration.
I try to add South migration tool to my Django app. I installed South by running python setup.py install and it is installed successfully. Now I can run migrate appname and schemamigration appname --a
I\'m curious as to how other Django devs manage their database migrations with South when developing with multiple code branches. Let me give a sample scenario.
加载中,请稍侯......