On Tue, Jan 8, 2013 at 2:59 PM, Chris Wolf <cwolf.a...@gmail.com> wrote:
> Ok, I think I have it all straight now and I really appreciate you > hanging in there to answer my questions. In closing, I'll make some > remarks, which are not time-critical to answer, since your answers > have already provided all I need to proceed. However: > > 1.) You said the DelayCollectionLoading was relatively new - so what > would people do in the scenario of one-to-many (or m-2-m) > and having huge numbers of child entities, before this feature was > introduced? > Why do you think we introduced this feature? :-) Seriously, this was a concern. If a one-to-many collection had a ton of elements, you better hope they were running on a 64bit jvm and had plenty of memory... > 2.) What do other OR mapping providers do? e.g. Hibernate or Datanucleus > JDO? > I believe Hibernate has similar functionality. I have no idea if Datanucleus does or not. > > Thanks again, > > Chris > > > On Tue, Jan 8, 2013 at 3:47 PM, Kevin Sutter <kwsut...@gmail.com> wrote: > > On Tue, Jan 8, 2013 at 2:20 PM, Chris Wolf <cwolf.a...@gmail.com> wrote: > > > >> Or is "non-indexed" referring to not traversing the collection while > >> adding or removing? > >> > > > > Correct. > > > > The word "proxy" is overloaded and is used in several contexts. OpenJPA > > proxies Collections (and a few other types like Dates and Timestamps) so > > that we can monitor updates to these object types. But, that is totally > > separate from the enhancement proxy mechanism that some JPA vendors > provide > > to monitor updates to the whole Entity. > > > > Good questions! > > Kevin >
