On 05/07/12 16:25, Anssi Kääriäinen wrote:
> Currently Django's session middleware saves sessions unconditionally
> in process_response. I have created a patch which skips session save
> on 500 responses. Reasons for this:
> 1. When saving the session after PostgreSQL query error into database
> b
Ask this on django-users
On Thu, Jul 5, 2012 at 11:50 AM, Tsachi wrote:
> Hi,
> I have a simple question, which I couldn't find an answer to it anywhere:
> In a django project I'm working on, a deleted user is marked as *
> is_active=False*.
> *I need to custom the User manager to filter out al
Currently Django's session middleware saves sessions unconditionally
in process_response. I have created a patch which skips session save
on 500 responses. Reasons for this:
1. When saving the session after PostgreSQL query error into database
backed session store, the save is guaranteed to fail d
Hi,
I have a simple question, which I couldn't find an answer to it anywhere:
In a django project I'm working on, a deleted user is marked as *
is_active=False*.
*I need to custom the User manager to filter out all is_active=False users.*
This is a project-wide requirement. In other words: I don't
