It shouldn't have a performance impact, since nothing really happens except the object is decoupled from the persistence manager.
In general, I recommend being very careful when doing this. There are a lot of places where it is working as intended even if behavior is unintuitive. You may want to explore using the low-level API instead if you are looking to retrieve and resave objects. On Wed, Jun 9, 2010 at 3:29 PM, Stevko <[email protected]> wrote: > Does anyone have experience with the runtime execution/performance > implications of using the JDO annotation detachable="true" in my > persistent object schema? > --stevko > > -- > 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 Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine -- 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.
