Fixed now.
See
https://groups.google.com/forum/?fromgroups=#!topic/django-users/FxTD5M0x-G8
for the resolution, if anyone runs into the same thing.
On Wednesday, April 10, 2013 5:04:58 PM UTC-7, Lewis Sobotkiewicz wrote:
>
> Seems to be caused by Django not sending the "request_finished" signal
Seems to be caused by Django not sending the "request_finished" signal,
which is also bizarre, unexpected behaviour.
On Wednesday, April 10, 2013 11:47:52 AM UTC-7, Lewis Sobotkiewicz wrote:
>
> Thanks, but I'm not using the Django development version. Apparently
> persistent DB conns will be a
Thanks, but I'm not using the Django development version. Apparently
persistent DB conns will be a feature of Django 1.6, but not 1.5.1.
I'm using RDS with MySQL 5.5.27. The only thing I've changed about the
infrastructure is upgrading Django to 1.5.1. If I downgrade to 1.4.5, DB
connections ar
https://docs.djangoproject.com/en/dev/ref/databases/#persistent-connections
On Wed, Apr 10, 2013 at 2:59 AM, Lewis Sobotkiewicz wrote:
> Hi all,
>
> I'm seeing some strange, undocumented behaviour when upgtrading to Django
> 1.5.1. I notice that it is holding onto MySQL connections after request
4 matches
Mail list logo
