Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Anyone can confirm if storing a property with a null value is most effective (in terms of datastore usage and quotas) than not storing anything at all (that is, a missing value) ?
It seems reasonable to think so and, in that case, I’d like to know how to avoid storing a property value instead of a null value when using JDO/JPA. I’ve only been able to avoid storing a given property with the datastore low level API.
I believe that not storing a property will save you a small amount of disk quota, but I’m not sure it is worth the effort, unless the amount of these “optional” properties is large compared to the amount of “always there” properties.
Of course, you can do a simple test by creating 2 sets of sample data using the low level API, and checking the Stats page to see how the sizes differ in the datastore.
One gotcha to be aware of is that AFAIK you can’t query for all entities that don’t have a property.