Is GAE team working on implementing the JDO feature (use default value for new field instead of throwing exception)? that will make data migration easier. -aj
On Mon, Feb 22, 2010 at 8:02 AM, datanucleus <[email protected]>wrote: > > 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. > > And in terms of the JDO implementation, the only thing needed for it > to handle that seamlessly would be to support the use of a "default" > value for any new field, so when reading old data that doesn't have > that field it would apply the default value to the field. This is > specifiable in JDO metadata, so is only waiting for the GAE/J plugin > to be modified to use it. > > -- > 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. > > -- AJ Chen, PhD Chair, Semantic Web SIG, sdforum.org http://web2express.org @web2express on twitter Palo Alto, CA, USA 650-283-4091 *Monitoring social media in real time* -- 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.
