Hi Will, Will Jaynes wrote:
It was my impression that the collection proxies would delay the loading of the objects in the collection until I actually tried to reference them. This does not seem to be true when using the ODMG api, as I am doing.Yes and no!
With the default settings in OJB.properties you are right.
By setting
ImplicitLocking=false you can turn off lock implicit (and recursive) lock acquisitation.
This will OJB not to load the collection proxy and register all elements of the collection.
Only disadvantage: you have to register objects explicitely to the transaction.
There has been a long discussion on the technical reasons of this behaviour on the list some time ago, so I won't go into details here.
cheers,
Thomas
I have an object graph with a lot of interconnections. Querying on one object has the potential to pull in alot of objects. So all of my collection-descriptors specify proxy="true". Regardless of this configuration, using the ODMG API, when I query on one object the rest of the object graph is also read in from the database. For each collection I see a "select count(..)" kind of query, and then a select to bring in the collection, and so on through out the object graph.
My test looks just like the "retrieving collections" example in the ODMG tutorial. My query specified the oid for an object. I expected to get materialize just that one object.
Am I missing something? I don't see how I can use the ODMG api if it is going to bring in the entire graph each time I need one object.
Thanks, Will
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
