Text properties were never actually lazy loaded. We only lazy loaded them to match the JDO/JPA spec. In practice, the entire entity was being read and we just weren't populating the entity.
Try running AppStats - though I suspect the deserialization shouldn't be *that* slow. -- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Thu, Nov 11, 2010 at 8:38 AM, Mark <mar...@gmail.com> wrote: > Hi, > > Is a Text property lazy loaded when I query for an instance of that > class? It seems to not be lazy loaded as of 2008, wondering if that's > still the case?: > > > http://groups.google.com/group/google-appengine/browse_thread/thread/81ac0c2bba6e37c8/291625c1099711b0?lnk=gst&q=text+lazy#291625c1099711b0 > > I ask because I'm wondering if a query for a class is spending time > deserializing my large Text properties, or waiting until I actually > access them (if ever) after the query is already performed, > > Thanks > > -- > 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 > google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com<google-appengine-java%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
