2013/8/8
> The exception is excited after connection with a database was lost and
> again regenerated(I start the application, execute a command postgresql
> restart, refresh the page of application and receive this exception)
Have you turned on persistent connections?
If so, you're seeing the
The exception is excited after connection with a database was lost and
again regenerated(I start the application, execute a command postgresql
restart, refresh the page of application and receive this exception)
--
You received this message because you are subscribed to the Google Groups
"Djan
2013/8/8
>
> That is the unit of a code was in section try...finally(in finnaly signal
> was excited signals.request_finished), now it isn't present.
> There is a feeling that in case of a code redoing it simply forgot to
> consider.
> If everything is made intentionally I ask to report about it (
Hello! Sorry for bad English.
I met the following error:
Traceback (most recent call last):
File
"/usr/local/lib/python2.7/dist-packages/django/core/handlers/wsgi.py", line
255, in __call__
response = self.get_response(request)
File
"/usr/local/lib/python2.7/dist-packages/django/core/ha
