Since you're building your own admin tool, you probably want to make use of Metadata Queries to find all the available namespaces. The docs are here:
http://code.google.com/appengine/docs/java/datastore/metadataqueries.html#Namespace_Queries <http://code.google.com/appengine/docs/java/datastore/metadataqueries.html#Namespace_Queries> 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 On Wed, Jul 6, 2011 at 10:04 AM, Ludovic Emo (Capgemini) < [email protected]> wrote: > What's would be the best practice in the case I want to segregate data for > my customers in namespaces but provide a full access to my admin/support > team on the data to be able to troubleshoot issues? > > Use case sample: > > 1) when my customers/end users see this grid, they will only see and edit > data of their namespace > => fully covered by the NamespaceManager.set() method > > 2) however when I'm connected and see this grid (same for the members of my > team to support the end users), I want to be able to access/see/edit all the > data of all the domains > > Ludovic > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine-java/-/TF68Wev9cbQJ. > 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. > -- 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.
