If you are using Objectify 3.0, the Key<?> is a simple wrapper for the native datastore Key - with all the same namespace consequences. In previous versions, the Key<?> -> Key conversion was done last-minute so it would "inherit" the namespace then.
Jeff On Sat, Jul 23, 2011 at 5:51 AM, Hugo Visser <botte...@gmail.com> wrote: > Well it appears that the entire key path for an entity group is bound > to one namespace. I am using Objectify in my app which doesn't have > the namespace in the keys but when checking out the low level Java api > that became apparent. > > On 22 jul, 12:48, Hugo Visser <botte...@gmail.com> wrote: > > Is it anywhere explicitly documented that the ancestor of an entity > > must have it's key in the same namespace as the entity itself? I'm > > using namespaces a lot in our app and in production I get an error if > > I try to do a transactional update of an entity with parent x in a > > different namespace than the entity that I'm updating. > > > > Is this intentional? If it is, I guess the dev server should also > > check this, my unit tests pass :) > > > > Hugo > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
