* While this should be rare, this does occur in the dm-is-list specs when testing against the yaml/in_memory adapters. * Possible optimization in the future might be to add #valid? methods to each gt/gte/lt/lte Comparison operator that returns false if the expected value is nil. This will cause the query to never execute, saving the comparison operator from being called when in an invalid state. The object may still need to handle invalid states when called stand-alone through.
This makes sure that when you try to declare a boolean property with a name "foo" and there's already a method called "foo?" it will raise an exception informing you that the name is not valid.
This reverts commit 22eb400.
* A Property could be defined that has the same name as another, but different options. * A comparison object has no need to use the slug since that is class specific, and the class' #hash is already factored in.