Open peterbe opened 13 years ago
Here's how I have to solve this for now:
./manage.py syncdb --noinput
./manage.py upgradedb --seed 0003
emacs migrations/0004_new_stuff.sql
./manage.py upgradedb --execute
@peterbe I remember seeing the issue you describe on MySQL years ago when I worked with that database and it seemed to happen randomly separate and apart from running migrations, but I can't remember what the cause was. I realize this issue was reported over a year ago, but am trying to clean things up a bit and tend to things I have neglected on this project. Is this still an issue with later versions of nashvegas?
Lemme compare how old our version is and see if an upgrade helps.
I'm stabbing in the dark here but I can't get a seemingly simple mysql set to work at all with nashvegas. It gets tangled in transaction juggling.
I have
And this doesn't work. There are no BEGIN or COMMIT or anything like that in any of the
.sql
files. As output I get this:So, I thought perhaps it's not right that the cursor is re-created in each iteration of the loop so I moved it outside and tried again. Now I get this:
One last time, I removed all my debugging modifications from upgradedb.py and moved away all files (migrations/*.sql) except the one called 000_initial_schema.sql and then I get this error:
I should add; my file (000_initial_schema.sql) is pretty big and it creates indexes and a bunch of other things.