|
Can I do any changes in the database and after that merge to the trunk? If yes, what must i do for this? What will be with migrations sequence? |
|
If you are maintaining your own branch, and are looking at how you would integrate "official" OSQA migrations, and your own branch migrations, look at the South documentation here: http://south.aeracode.org/docs/tutorial/part5.html#team-workflow I'm not fully up to speed on how that works, but it looks like it solves your possible problem. |
|
I wasn't able to figure out if you are asking about how to create automatically database scheme migrations? If so you have to use the python manage.py schemamgration forum --auto command. No, I want to know, is it possible to change database structure and after that well do a merge with trunk of the OSQA?
(25 Jul '11, 20:34)
expert
What kind of changes are you talking about? Change the db directly, or the osqa models? Anyway, you can do whatever you want with the db, but at your own risk, OSQA, like any other software that uses a relational database to sore that, expects a certain schema to be present..
(25 Jul '11, 20:51)
Hernani Cerq... ♦♦
|
@expert, please edit this to rephrase the title as a proper question.