No, it should be fine UNLESS you want to load all these child objects in a single request. As a rule of thumb, load as little data as possible. You may need to denormalize (the datastore isn't relational anyway) for additional read performance.
For a better answer, you may want to describe what it is you are trying to do. On Mon, Apr 12, 2010 at 6:57 AM, ailinykh <[email protected]> wrote: > Hello, everybody! > I have objects with owned one to many relationship. Child table is > supposed to grow, each parent eventually will have thousands or even > more child objects. > May it cause any performance issues? Is there any best practice to > handle this situation? > > > Thank you, > Andrey > > -- > 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]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- 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.
