i agree with you - that it would be more intuitive maybe you should repost the ticket then
a param "exclusive"=>true (default false, of course) could still make the current behavior available :) if needed at all On 13 Feb., 02:04, Ryan Schmidt <[email protected]> wrote: > I was surprised to discover that the "range" validator is exclusive, not > inclusive. > > I've now built my own "rangeInclusive" validator in my app_model.php to use > everywhere. > > Someone filed a bug about this three years ago, and there is a patch, and it > is not closed... > > https://trac.cakephp.org/ticket/4483 > > I guess the question is.... why is this? -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
