Hi all. Still feeling my way through Django development, working on my first app still, and I've hit what looks to be a huge hurdle: Django has no in-built mechanism for dealing with making changes to the structure of models.
Okay, fine, I can understand the reasons for that, and while I think it would still be nice to at least provide the option to those of us who want to risk our data on a series of automatically-generating ALTER TABLE statements, I can understand why the folks behind Django didn't give it to us. That said, I can't be the only one who has planned out a long sequence of point releases as I build my app and release new functionality on a regular basis, a lot of which will require not just new models but changes to existing ones. As one example, I'm currently adding the ability to "tag" blog entries; my BlogEntry model already existed, of course, and adding tags=models.ManyToManyField(Tag) to it resulted in syncdb, obviously, not creating the new linking table. (Well, maybe it's not obvious at first glance that the creation of a new table would not occur since it's triggered by a change to a model who's table already exists, but we'll get past that, too.) So now we get to the question: As I can't even begin to conceive of myself being the only person in this boat, I have to believe there's one or more generally-accepted and "good" ways of dealing with updating database structures while maintaining data, aren't there? What method(s) do y'all use when you need to do things like this? TIA, Travis --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
