What is Opf3? Why is Opf3? How is Opf3? All these burning questions and issues discussed here.
| ||Hi Al, |
I know! Opf3 has been designed to be very open to add new query languages and storages. That was one of the main goals. You could use Opf3 to query and kind of storage that is not limited to ADO.NET, actually.
That has pros and cons. Pros are that Opf3 is very flexible when it comes to add new storages to the framework. And that you can extend it to any query language that you want and your storage understands. Cons are that you can extend it to any query language tha your sotrage understands but Opf3 doesn't...
Therefore the IdentityMap is really only here to make sure you never have two objects in memory that represent the same row in the database.
As said: caching might help you to reduce your roundtrips a lot. If caching would fail and the IdentityMap is enabled you would be sure to only have the same object once in memory :)