simone.dalmasso at gmail.com
Tue Jun 13 11:59:16 PDT 2017
Ah I see.
In master you can just add the new migration with makemigrations. We will
squash migrations upon release. as you say in development is ok to have the
separate as we prolly don't want to destroy the db every time
Il giorno mar 13 giu 2017 alle 20:55 Goran Mekić <meka at tilda.center> ha
> On Tue, Jun 13, 2017 at 06:52:34PM +0000, Simone Dalmasso wrote:
> > Sorry it is not clear to me what the issue is. The migrations always
> > reflect the data model. We actually all work on master and contribute tu
> > it.
> Maybe it's better with an example. Let's say you add some code to 26_to_27
> migration. How do I apply it? Simple "manage.py migrate" doesn't work, as
> that migration is already applied on my machine.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geonode-devel