Django ORM: caching and manipulating ForeignKey objects?

Django's ORM does not implement an identity map (it's in the ticket tracker but it isn't clear if or when it will be implemented; at least one core Django committer has expressed opposition to it ). This means that if you arrive at the same database object through two different query paths, you are working with different Python objects in memory.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.