Re: Database connection retry

Hello, > On 8 Mar 2017, at 21:23, Chris Foresman wrote: > > I'll chime in to say I've had a similar problem related to the shell and I > couldn't sort out how to address it. In such situations, AFAIK, the following works: from django.db import connection

Re: Database connection retry

Chris, whilst I'm sure you could work something out, it probably wouldn't generally work as database connections contain a lot of state, such whether or not we're in a transaction and variables. On 8 March 2017 at 20:23, Chris Foresman wrote: > I'll chime in to say I've had

Re: Database connection retry

I'll chime in to say I've had a similar problem related to the shell and I couldn't sort out how to address it. Our database servers will drop connections that last longer than 10 minutes. So basically can never do a task I might otherwise use the shell for that would take longer than 10

Re: Feature idea: forms signals

On Wednesday 08 March 2017 18:18:26 Melvyn Sopacua wrote: > On Monday 06 March 2017 10:10:41 David Seddon wrote: > > Hi all, > > > > One thing I've always found challenging with Django is to adjust the > > functionality of forms from other apps. An example might be to add > > an extra field to a

Re: Feature idea: forms signals

On Monday 06 March 2017 10:10:41 David Seddon wrote: > Hi all, > > One thing I've always found challenging with Django is to adjust the > functionality of forms from other apps. An example might be to add an > extra field to a login form provided by a third party module. > > What I end up doing

Re: In-memory queryset

Hi Paul, Depending on your use cases django-modelcluster might be of some use: https://github.com/wagtail/django-modelcluster It's primarly for dealing with a bunch of models that have foreign key relationships, but before they're written to a database (i.e before they have primary keys that