On Saturday, September 19, 2015 at 8:39:54 AM UTC-5, Shai Berger wrote:
>
> Hi,
>
> On Saturday 19 September 2015 14:02:38 Markus Holtermann wrote:
> > On September 19, 2015 6:38:59 AM GMT+10:00,
> > Flavio Curella > wrote:
> > >
> > ># settings/production.py
> > >MIGRATION_FAKE = (
> > >
On Saturday, September 19, 2015 at 6:03:06 AM UTC-5, Markus Holtermann
wrote:
>
> Hi Flavio,
>
> This sounds like a very risky and scary proposal, to be honest. The
> recommended way would indeed be to fake the initial migration(s) on
> production.
>
>
Could you elaborate on this point? I ha
Hi,
On Saturday 19 September 2015 14:02:38 Markus Holtermann wrote:
> On September 19, 2015 6:38:59 AM GMT+10:00,
> Flavio Curella wrote:
> >
> ># settings/production.py
> >MIGRATION_FAKE = (
> >
> >('transactions', '0001_initial),
> >
> >)
>
> This sounds like a very risky and scary propos
Hi Flavio,
This sounds like a very risky and scary proposal, to be honest. The recommended
way would indeed be to fake the initial migration(s) on production.
Since it seems to me that this would only ever be needed once (you said devs
should just run the migration locally and the table is too
I'm not sure if this warrants a DEP, so I've decided to post it to the list
first. If this needs to be a DEP, just let me know and I'll follow the DEP
process.
Rationale
-
Assume the following scenario:
1. At some point in history, project A was deployed in production and was
very
