Best practice suggestion for custom migrations (starting at 0100)

[vdb...@edoburu.nl]

Hi,

While experimenting with custom migrations, I ran into the difficulties of upgrading Oscar.

However, it turns out if you start your custom migrations at a higher number (say 0100, 0101, etc..),

South will happily execute any newly added migrations when you upgrade Oscar.

Hence my suggestion, would it be an idea to mention this in the documentation?

Thanks in advance,

Diederik

[Maik Hoepfel]

Hi Diederik,

I'm afraid it's not as easy as that. I'm pretty sure that when you
upgrade Oscar, South will not run any new Oscar migrations because
they're hidden by your custom migrations with the higher migration number.

Cheers,

Maik

> --
> https://github.com/tangentlabs/django-oscar
> http://django-oscar.readthedocs.org/en/latest/
> https://twitter.com/django_oscar
> ---
> You received this message because you are subscribed to the Google
> Groups "django-oscar" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to django-oscar...@googlegroups.com
> <mailto:django-oscar...@googlegroups.com>.
> Visit this group at http://groups.google.com/group/django-oscar.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-oscar/2c8d09af-3f61-4f08-b45c-34d834a93fd2%40googlegroups.com
> <https://groups.google.com/d/msgid/django-oscar/2c8d09af-3f61-4f08-b45c-34d834a93fd2%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.