Hi, I successfully implemented a tree data model using JPA and extensions using this type of annotation:
@Id @Extension(vendorName = "datanucleus", key = "gae.encoded-pk", value = "true") @GeneratedValue(strategy = GenerationType.IDENTITY) private String id; with bi-directional relationships between the parents and children. The leaf of that 6 level tree end up with primary keys that show up as this in the datastore viewer: aglzZW5zb3JpZXRyWwsSBFJvb3QYswsMCxIHTmV0d29yaxi0CwwLEgpTdWJOZXR3b3JrGLULDAsSB0lPQm9hcmQYuAsMCxIISU9TYW1wbGUY2QsMCxINSU9TYW1wbGVWYWx1ZRjaCww Considering that there will be a lot of such leaves, and that these leaves will each have very little data, does that mean that my datastore daily bill will be significantly affected by this type of structure? Would making leaves top level entities with a single relationship with their parent make a big difference ? (i.e. use a LONG primary key instead of the extension gae.encoded-pk) Or would the direct usage of the app engine datastore Key type make another big difference in datastore space usage ? thanks, -- Claude -- 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/-/Vdnkx9anxHQJ. To post to this group, send email to google-appengine-java@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.
