Week ending December 13, 2020.
*Triaged: *
https://code.djangoproject.com/ticket/32245 - Replacement for
./manage.py test --liveserver? (invalid)
https://code.djangoproject.com/ticket/32247 - "App does not have
migrations" message could be more helpful (invalid)
https://code.djangopr
Hi,
On Dec/16/2020, Muskan Vaswan wrote:
> Carles Pina I Estany: While I understand what you’re trying to do I
> don’t know why we are trying to avoid COUNT is there a best practice
> associated with this that I don’t know about?
We are (or... I was :-) ) trying to answer this question as cl
On Dec 16, 2020, at 2:17 PM, Carles Pina i Estany wrote:
My message is
that it probably can be done without COUNT if need to be and show "more
than X rows" instead of the exact number of rows.
Well yes this makes sense to me now,
but only in the sense that we would first check whether some quer
Hi All,
I would like to solicit some further comments regarding #32267. The main
question is:
Should Django support unapplying migrations in a branch?
Typical use case:
$ git switch otherdeveloper/feature
$ manage.py migrate
Applying app.0051_migration_from_feature... OK
Applying app.0052_migra
>
> manage.py migrate app 0050_migration_from_master will unapply too much
> (specifically, all the subsequent migrations from master)
I don't follow you. This is exactly the thing I do, migrating back to the
last common migration.
On Wed, 16 Dec 2020 at 17:21, Roman Odaisky wrote:
> Hi All,
>
On Wednesday, 16 December 2020 23:38:55 EET Adam Johnson wrote:
> > manage.py migrate app 0050_migration_from_master will unapply too much
> > (specifically, all the subsequent migrations from master)
>
> I don't follow you. This is exactly the thing I do, migrating back to the
> last common migra
On Wed, Dec 16, 2020 at 1:39 PM Adam Johnson wrote:
>> manage.py migrate app 0050_migration_from_master will unapply too much
>> (specifically, all the subsequent migrations from master)
>
>
> I don't follow you. This is exactly the thing I do, migrating back to the
> last common migration.
I t
On Thursday, 17 December 2020 02:28:02 EET James Bennett wrote:
> On Wed, Dec 16, 2020 at 1:39 PM Adam Johnson wrote:
> >> manage.py migrate app 0050_migration_from_master will unapply too much
> >> (specifically, all the subsequent migrations from master)>
> > I don't follow you. This is exactly
Ah right, thanks for elaborating. I normally stick with a single app and a
linear migration history. Avoiding merge migrations is good for a number
of reasons and avoids the situation your diagram covers - see my recent
package django-linear-migrations which help with that:
https://adamj.eu/tech/2
