Embedding is the same as defining the fields on the parent. Assuming you need the embedded data most of the time, and it is small, I think you gain a performance boost as to load the data you only load one entity, not two. This assumes the embedded class is small in size, and you require its data. The data would not be lazily loaded.
If you hardly use its data, or it is large and you only sometimes need it, you will loose performance as it is loaded each time. Also using embedded means you can search the parent via the embedded fields. Otherwise you cannot. On Aug 26, 7:25 am, Larry Cable <[email protected]> wrote: > I'd be surprised if you can even get them to work!!! I am having no > end of trouble > getting a pretyt basic @Embedded scenarios to work ... > > good luck! > > On Aug 25, 2:19 pm, "fx.mueller" <[email protected]> wrote: > > > > > Hello, > > > I just went through the getting started documents and have a question > > regarding embedded classes, which I haven't found discussed elsewhere > > (maybe because it is trivial ;-): > > > What are the performance implications of defining a class as embedded? > > > Is it the same as if the fields of the embedded class are directly > > defined in the parent class? Or do I gain any performance benefits by > > defining a class as embedded - maybe because the fields of the > > embedded class become part of a different index? Or maybe because the > > fields of the embedded class are "lazily" retrieved if the parent > > class is retrieved? > > > thanks, franz- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
