Runtime validation of field names used in criteria API [DATAMONGO-165]

[spring-projects-issues]

Mark Pollack opened DATAMONGO-165 and commented

made a refactoring from 'name' to 'firstName' and ended up with a NPE when trying to remove the object (inadvertently passed in 'null' to template.remove(). Optionally we can enable validation of the field names so they can checked at runtime against the class to give a more descriptive error and w/o hitting the DB. This I believe is done in morphia under the categorization of 'type-safe' query

---

Affects: 1.0 M3

[spring-projects-issues]

Scott Hernandez commented

Yep, morphia supports this as well as field aliases (@AlsoLoad) so you can query old field names while migrating data. In addition data types are checked for each field as well to warn if you are using the wrong type