I believe Set is implemented at the datanucleus layer, so this should be fine. I'm not sure what'll happen if you have a List with duplicate properties, however.
The way I would test this is to create a new app ID version and deploy code that changes to a Set. Don't set the version as default and test it at: http://version_name.appid.appspot.com Since all versions share the same datastore, you'll be able to quickly determine if this causes any issues. -- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Thu, Nov 18, 2010 at 6:39 AM, OdysseyFX <[email protected]> wrote: > I have some jdo objects with many to many unowned relationships in the > datastore already. This was done with List<Key> and I have many objects > already persisted in the datastore. I want to switch this Key collection to > Set<Key> in the object however I'm not sure how the datastore will respond > to that. Is the datanucleus implementation storing the data in a more > abstract Collection manner and then simply building a List or Set each time > and populating it, or is it more of a "once a Set always a Set" situation? > > Thanks! > > -- > 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]<google-appengine-java%[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.
