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
Another idea: instead of an enum, how about using the datetime.date.year,
month, day attributes?
If you prefer the enum, I don't really see an obvious place for it, so use
your best judgment and make it importable from contrib.admin I suppose.
On Saturday, September 19, 2015 at 12:38:10 AM UTC-
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
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
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 the infrastructure side, I added Python 3.5 support to Jenkins (Django
1.9 will support it) and removed our own “wheelhouse” of cached wheels
since Pip 7+ now provides that functionality. I also completed the “new
stable branch tasks” for bootstrapping Django 1.10 which can be merged
after
