I mean I made the proposal, but one drawback will be when linking to
Postgresql Docs, what if they change the links? I mean that's barely
happend in the past, however the "
http://www.postgresql.org/docs/current/static/non-durability.html"; is
fairly new. (9.x).
So we need to track every major upgr
I made a small comment about the URL form. To my ear, the text could use a bit
of wordsmithing, but I think it's the right content.
On Jul 20, 2015, at 3:10 AM, Federico Capoano
wrote:
> Errata, PR link is https://github.com/django/django/pull/5021 - sorry
>
> On Mon, Jul 20, 2015 at 11:42 A
On 07/20/2015 11:47 AM, Shai Berger wrote:
> On Monday 20 July 2015 18:47:07 Carl Meyer wrote:
>>>
Personally I don't really see much use case for this feature
except as a workaround for reusable apps that generate spurious new
migrations based on settings changes
>>>
>>> I've also s
On Monday 20 July 2015 18:47:07 Carl Meyer wrote:
> >
> >> Personally I don't really see much use case for this feature
> >> except as a workaround for reusable apps that generate spurious new
> >> migrations based on settings changes
> >
> > I've also seen it with apps that use "EmailField" with
On 07/19/2015 06:14 AM, Anssi Kääriäinen wrote:
> To me it seems the choice of doing migrations for app/model should be
> done by the author of the app.
>
> How about model/app level setting migrations_mode, where the choices are
> auto, manual and never. Auto is the defaul and behaves like curren
Hi Shai,
On 07/19/2015 01:52 AM, Shai Berger wrote:
[snip]
>> It seems like what Marcin wants is more of a "don't ever create new
>> migrations for this app, but go ahead and use its existing ones
>> normally" flag (thus something that affects only `makemigrations`, not
>> `migrate`).
>
> That's
Errata, PR link is https://github.com/django/django/pull/5021 - sorry
On Mon, Jul 20, 2015 at 11:42 AM, Federico Capoano
wrote:
> Thank you for all the feedback.
>
> I opened this PR with the proposed addition to the docs:
> https://github.com/django/django/compare/master...nemesisdesign:patch-1
Thank you for all the feedback.
I opened this PR with the proposed addition to the docs:
https://github.com/django/django/compare/master...nemesisdesign:patch-1
Let me know if there's anything I can improve.
Just a final note: I think this solution is not the optimal one, let
me explain you why.
