What about the ability to move an entity to a namespace? On Sep 23, 10:57 pm, John Patterson <jdpatter...@gmail.com> wrote: > On 24 Sep 2010, at 02:55, Mouseclicker wrote: > > > API. The need to set and later reset a global setting is dangerous and > > error-prone. Probably that's what Guillaume mentions with "The fear I > > had was when seeing a static methods being used. I'm always afraid > > when I see 'static' somewhere." Me too! > > The namespace is not global or static but stored per-thread so it must > be set for every request e.g. in a servlet Filter. There is no > problem setting it for a single operation if it is reset in a finally > block. > > I personally like the way that the namespace API is completely > separated from other APIs. In fact, I would prefer it if the memcache > API namespace did not override the namespace API namespace... that > caused a subtle bug the other day. > > It really is very important to be able to see all the stored data in > the datastore viewer without requiring the user to enter the > namespace. Especially as the user could be billed for data they > cannot delete.
-- 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.
