On Sat, Apr 25, 2015 at 2:15 PM, Javier Guerra Giraldez <jav...@guerrag.com> wrote:
> > > with South i used to save them to the repo too and push whole to > production. haven't tried Django migrations yet; is there any > difference that make this more appropriate? > > Hmmm, good question. That was kind of my question. With South I always saved them. This is my first project with using Django migrations. There doesn't seem to be much difference. > if you don't store migrations, then you have to generate them on each > production update, right? if so, wouldn't they count as untested > code? how about manually tweaked, or data migrations? > > That will certainly be true once you start using a staging or production server. But before they they are just a kind left over creative ideas. :-) Not really useful for anything in the future, AFAICS. ============================================ Timothy Cook LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook MLHIM http://www.mlhim.org -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2B%3DOU3VL4HEPW%2BFLAgRsh0Qfhk_Kh98%2BtO%3DyG1wN%3Dy0-C1n%3DJw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
