Yes, it's fetch groups. The store (pre-groups) took all this into
account, however the lack of central management for some of it caused
it to be pretty error prone. Those problems were related to
Continuum's design, not anything to do with the use of JPOX (and
something that'd be encountered in iBatis, or JPA, or anything else
we used).
On 28/12/2006, at 7:33 PM, Rahul Thakur wrote:
On 27/12/2006, at 7:10 PM, Rahul Thakur wrote:
Updates to any children hanging off key entities should cascade.
This makes sense if and only if the children are dependent. So,
for build definitions - that's right. Profiles and such are all
'links' and so will be managed by the normal foreign key construct.
Thanks Brett!
I might need some help with Jpox when I hit this scenario. It would
be nice to have some sort of 'lazy' intialization to happen when
children hanging off key entities are retrieved, but not sure yet
what Jpox offers (fetch groups?).
Cheers,
Rahul
