I haven't programmatically tested this for problems yet, but looking at the datastore viewer for the app that I created for the @MappedSuperclass test case (other thread), all the child objects seem to have id=1 rather than pulling from a common ID generation pool as is done on the localhost development server. This is disturbing because EntityManager.find(Long) is supposed to work for all Kinds, AFAIK, and does in the dev server.
Should I expect Key.getId() to return a globally unique number for all persisted objects, or is it only unique relative to its parent Key? (The objects in question are using Key references for the underlying classes, not Long references, to avoid other problems with Long @Id fields noted in other threads.) -- 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=.
