I'm sure this is a max.ross question, but archiving the answer would be useful.
The JDO/JPA docs are not very clear about the use of collection types in field mappings. I know that I can create a List<E> field marked @Basic (for simple element types) or @OneToMany, but is that really optimal? I have read a few threads here that allude to list-ordering being slow, which naturally points towards Set<E> as an alternative. Post-sorting is "just code" anyway.... What if I want duplicates to be possible but don't care about list- ordering (in the interest of speed)? If the field is declared simply Collection<E>, would this improve performance? In the original object initialization, it might use an ArrayList or LinkedList; but when working with a proxy-enhanced object, does the declaration of Collection allow datanucleus to use a better type that isn't constrained by list-ordering slowness? -- 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.
