[appengine-java] How to handle class version issues in DataStore

2012-03-12 Thread andrew
Nulls (Java), if the object can have null as a value. E.g. Integer can be null, int cannot. I think this is explained in GAE/JDO documentation. -- 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

Re: [appengine-java] How to handle class version issues in DataStore

2012-03-12 Thread Matthew Jaggard
This answer also applies to the low level datastore and Objectify. I can only assume JPA works the same way. On Mar 12, 2012 7:40 AM, andrew andrew.macken...@bcntouch.com wrote: Nulls (Java), if the object can have null as a value. E.g. Integer can be null, int cannot. I think this is

Re: [appengine-java] How to handle class version issues in DataStore

2012-03-12 Thread Jeff Schnitzer
That's not quite correct - in the low-level datastore, this isn't an issue because absent properties will simply be missing from the Entity. In Objectify, absent properties are ignored. You can add fields of primitive types without ill effect - they will simply have their default values. This

[appengine-java] How to handle class version issues in DataStore

2012-03-11 Thread Yogesh Naik
Hello, I have a question related to App engine Data Store. Lets say I have a simple POJO class like this: public class Employee implements Serializable { private String name; private Date birthDay; ... ... } I create an object of this class and store it in Data Store. After this lets say if I