Templates error on partial rendering

I have a case where we use django templates, but it really makes no sense to render the templates if a value is not passed in the contentx, and it should just fail.. I don't find anywhere how to force that though, I understand the default of failing silently but there should be a way also to fa

Re: Django migrations taking all the memory on Django 1.9

oing things 100% properly while running migrations just for tests. I think that in general if there was just a way to render all the SQL that needs to be run statically for tests it would be great. On Friday, August 5, 2016 at 11:07:56 AM UTC+1, andrea crotti wrote: > > We have a very big Djan

Re: Django migrations taking all the memory on Django 1.9

hile testing. There's a ticket to make that a bit > easier: https://code.djangoproject.com/ticket/25388 > > On Saturday, August 6, 2016 at 6:07:04 AM UTC-4, andrea crotti wrote: >> >> >> Ok great thanks for the answer Markus. >> And yes I can try to help, it&

Re: Django migrations taking all the memory on Django 1.9

at you disabled migrations for an app > (something_else) that's a dependency of another app that doesn't have > migrations disabled (something). That isn't permitted. I guess there's no > good solution for your requirements as of now. > > On Monday, August 8,

Re: Django migrations taking all the memory on Django 1.9

o Django 1.10.x either. Hopefully that doesn't > demotivate you from contributing an improvement. > > > https://docs.djangoproject.com/en/dev/internals/security/#supported-versions > > On Monday, September 5, 2016 at 9:55:30 AM UTC-4, andrea crotti wrote: >> >> T

Sqlmigrate generated SQL

Related to this other thread: https://groups.google.com/forum/#!msg/django-users/V8Ei2qZJ8VI/bFUeY2wTAQAJ;context-place=forum/django-users I'm working on trying to find a workaround for migrations killing our local/CI servers, until there is a better fix in Django stable.. So started this proje

Re: Sqlmigrate generated SQL

e SQL after would not apply because the schema changed in the meanwhile.. On Tuesday, October 4, 2016 at 10:41:25 AM UTC+1, andrea crotti wrote: > > Related to this other thread: > > > https://groups.google.com/forum/#!msg/django-users/V8Ei2qZJ8VI/bFUeY2wTAQAJ;context-place=forum/

Migrations with multiple databases

We have a couple of databases with a tiny number of tables, but django-migrations has still go through all the migrations anyway. So even if the SQL itself is nothing it still takes a massive amount of time and memory for the usual known issues with migrations on big projects. I guess it works t

Re: Migrations with multiple databases

se apps don't have migrations. > > Cheers, > > /Markus > > On Tue, Oct 25, 2016 at 08:05:46AM -0700, andrea crotti wrote: > >We have a couple of databases with a tiny number of tables, but > >django-migrations has still go through all the migrations anyway. > >S