Re: Migrations During Development

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVPB+DAAoJEC0ft5FqUuEh7iUP/jIeR991JTg1Mo+hEpXmRlsP
xoatzlDuTRcKzIPpR6al9ZmUb7MKupsoBQhv7ILvDBbn6I7uZ247qSfDsiAn4q6L
W1UgNwjGJwVvI5Xawmeizv2Qg769euYQD0L5slAE+cj1FWZm5JNVBw7ytZxlaohO
dQcQiUL2GDqq9YwO2tcw4EolsVYSCq3HMY/JSY+NtYDMRL45ja7SjL1sInm1Ug9e
2nIvpEMdMpac8T5xrNXDeSxtiSyNRbpwZ6xGD2tbGlUg2arndNwTUKpslRyGUr3Y
K81MVlulQgmdz6l5bgD8eKejd2kD0BeOQky5XfvU3nUN4BbqABSLLKaI3SLg1dmY
VVbOhhj5L4nl11VHaeqd80CPmAJ/sh9rPXaym3qVys3Qcr3o/sV2K0b+W1QfXgNb
IT7wPGFBQTdTOyRyKwL6BXPlPprrYd1Syo6cr0mWNNzUmEvy3o7Zp9zLD5pzRsgT
Qm+Bg+tYPeHaiQcqvJOpBPWHZVGcwFJQHSj1flvpb9AT10dlofRF9EhOTRhBB6rb
CmqP3MAwEXo4vNApgQS5PeRqmiAG77gqLb3LpoUyQi7pfYqXcF1nqPXNxV2cNBxB
nQG0cDfnwfM9LqwTsxa3eTt0J3q1A5H6Q3s/BcC+GaWB79nakpwDHPUwQ3+gYFKO
NXBt7ydtQQk3S8KxJY/6
=M76H
-----END PGP SIGNATURE-----
On 04/25/2015 11:15 AM, Javier Guerra Giraldez wrote:
> On Sat, Apr 25, 2015 at 12:08 PM, Timothy W. Cook <tim@mlhim.org>
> wrote:
>>
>> On Sat, Apr 25, 2015 at 9:48 AM, Jorge Andrés Vergara Ebratt
>> <javebratt@gmail.com> wrote:
>>>
>>> Are you using version control like GIT? I save the migration
>>> folder with the __init__.py in GIT, nothing else, because al the
>>> migrations will be diferent in the diferent servers.
>>>
>>
>> This is probably what I should have done. I have been saving them
>> all to the git repo.
>
>
> 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?
>
> 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?

Migrations should be committed to VCS in both South and in Django
migrations.

Carl

--
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+unsubscribe@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/553C1F83.60105%40oddbird.net.
For more options, visit https://groups.google.com/d/optout.