google app engine - Dereferencing two ReferenceProperty's that points to the same object in the datastore -

I was reading about curious loading which would tell me about efficient deering on GAE.

Is it true, that if I point out the same object in the datastore due to two contextual practices, the framework does not maintain any type of identity map and two separate requests Receives? There are various examples returned to objects and changes on one do not clearly appear on the other.

Is not it less than ideal? I am coming from a SQLite background, where I feel really comfortable with the session pattern.

That's right, Guido's new project demonstrates this mapping, but the current DB framework does not . The reason for this is what you want: If a single institution is brought and modified in two different parts of the code, it can cause unwanted side effects. The natural hope is that if you get the object, then it is yours and nothing is going to change it under you, unless you want it.

At the time you want to delete the batch of the same entities, you can convert the list of keys into the first set to eliminate duplicate fetches.