Docs link:
https://docs.djangoproject.com/en/1.11/howto/writing-migrations/#controlling-the-order-of-migrations
On 7 July 2017 at 22:53, Andrew Godwin wrote:
> There is already a run-before constraint you can add to migrations for
> exactly this purpose! It's called "run_before" and is in the sa
There is already a run-before constraint you can add to migrations for
exactly this purpose! It's called "run_before" and is in the same format as
the dependencies IIRC.
Andrew
On Fri, Jul 7, 2017 at 6:36 PM, Carl Meyer wrote:
> On 07/07/2017 05:09 AM, Patryk Zawadzki wrote:
> > Right, and
On 07/07/2017 05:09 AM, Patryk Zawadzki wrote:
> Right, and one reason for generating those "no-op" migrations is that
> they aren't actually no-ops, if you value being able to write data
> migrations in Python using the ORM. They keep the historical Python
> models accurate.
>
> I
>
>
> Anyway, I don't want anyone to think that I complain as I don't have the
> resources to write yet another migration tool and both South and Django
> migrations beat writing SQL by hand.
>
Have you tried Liquibase ever? It is very reliable, unfortunatelly it is
missing automatic changeset
W dniu wtorek, 4 lipca 2017 23:49:54 UTC+2 użytkownik Carl Meyer napisał:
>
> On 07/04/2017 07:04 AM, Patryk Zawadzki wrote:
> > Have DB backends understand certain field types expressed as strings
> > ("varchar", "text", "blob", "decimal" and so on).
> >
> > Possibly some backends could implem
