The only thing we could do was to write some special low-level api code
to update the schema properly (low-level api is more flexible and
doesn't have issues abou querying old or new data, they are all entities
with list of fields).
For example, when adding a field that uses a primitve type to an object.
You can't query all objects with JDO pretending to store them in the
recently modified object, because null cannot be asigned to the non-null
field, but you can query the objects using the low level api and set a
default value for the new field.
Of course this is far far away from being a efficient way of updating
your schema, but I don't know whether there's some better (at least for
java)
Regards,
Esteban
El 22/02/2010 8:11, opok escribió:
What about rename/add/remove persistent field or change its data type?
I found there are some exceptions thrown out while querying on old
data. What should I do? Any document for this problem?
--
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=en.