Closed aboutaaron closed 10 years ago
Something we should definitely get around to, though I think we're in for a big number of revisions yet if we take this app as far as it can go. Since we're at an early stage and we routinely smash and grab the data, I'm okay with blowing up my database repeatedly but if you'd find it useful now I say run with the idea since we will need it someday.
Makes sense. Since development is active, we'll just save migration history for version 1.0, although it may be worth adding it sooner if we see ourselves editing more models in the future.
Moving to #76
@palewire I see you added a new field:
Perhaps we should have some sort of migration history setup so we can add and remove columns at will. I don't know if bumping to Django 1.7 would help. It looks like you may be using it already but
requirements.txt
still asks for Djnago 1.6.x.