Malcolm Tredinnick wrote:
> In hindsight, I probably wasn't clear as to why I'm suggesting this:
> there are a lot of places where Django would like to write to your
> database (sessions, auth lookups, ...). You can configure around and
> away from each of those in turn, but, if this were me, I'd save on brain
> wear-and-tear by letting Django behave normally until and unless I
> wanted to talk to this other read-only database and then I'd explicitly
> point my database connection in that direction. I have no stronger
> technical reason for my suggestion than that; it's primarily intuition
> and gut-feeling, but you don't have to tell anybody that.
Thanks Malcolm, that vague use-case was pretty much what I was thinking
too, I'll read through the article and see what insights it has :-)
Cheers!
Tom
--
Tom Eastman / +64 3 479 7073 / [email protected]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
