This gets ugglier at each step, think twice before doing this.
Django uses thread storage for django.db.connection, so what seems a simple
object is unique to the request and safe. The quick and dirty way is to
place a middleware after auth, and set something in django.db.connection.
PD: django.db
Hey Matias.
Many thanks for your answer. This is what my 'new' manage.py looks
like:
http://dpaste.com/58713/
and it seems to work. At least no data is saved any longer :)
But next question is not far away:
I can use pass or return forig(self) according to if i'd like to save
or not (is this o
Monkey patch django.db.model.save
Where? in manage.py?
On Tue, Jun 23, 2009 at 12:56 PM, ReneMarxis wrote:
>
> what i forgot to say: Of course i don't like to change all models-
> code. Some 'global' solution is what i am looking for.
> >
>
--~--~-~--~~~---~--~~
what i forgot to say: Of course i don't like to change all models-
code. Some 'global' solution is what i am looking for.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, se
Hello
i have a question if something is possible to implement :)
i need some demo functionality in my django app and i'd like to
realize it by having some flag in the user's session that defines if
data should be saved at all or not in the whole app (for the session
user).
That way i could just
5 matches
Mail list logo