i agree that it wouldnt hurt to specify the rules for numeric values a little bit more precisely :) if you provide a ticket and a patch, i am sure it will be considered for 2.0
On 24 Feb., 09:19, Ryan Schmidt <[email protected]> wrote: > On Feb 14, 2011, at 10:12, John Andersen wrote: > > > You always have the opportunity to make your own validation rules, see > > the CakePHP book at: > >http://book.cakephp.org/view/1179/Custom-Validation-Rules > > > I don't think the CakePHP team can take into account all the possible > > kinds of validation rules that we would like to have. > > But feel free to make the suggestion to the team for the validation > > rules, that you would like to see in future CakePHP versions. > > I know that I can define my own validation rules; I have already done so in > my project. > > I'm not asking for CakePHP to provide all possible validation rules for every > possible scenario; I'm asking it to provide the most common types of > validation rules that almost every project will need to use. Integer and > especially unsigned integer validation are in that category. If I am building > a ticket-ordering site where I want to know from the user how many tickets > they want, then I will have an unsigned integer field in my database for > that, and I will want unsigned integer validation on it. But when I bake this > model, CakePHP will suggest that I would want "numeric" validation on it. If > a user enters that they want 3.14 tickets, the numeric validation will allow > that (which will, when saved into the database, be truncated to 3), whereas I > would want my model's validation to display an error message to the user > instead. > > I am a new CakePHP user; the humor of the "female needs help!" thread > notwithstanding, I find it entirely relevant to mention this, since it means > I do not know if I am using CakePHP correctly. Bug trackers are great places > to write up things which are bugs; I was not yet sure whether the behavior I > observed was a bug or missing feature (though it certainly seemed like it to > me) or merely me not knowing how it is meant to be used. The reasons I wrote > to this list were: > > * to verify whether I have understood correctly that CakePHP does not have > this (to me) basic and fundamental feature built in; > * to inquire whether anybody else has noticed this before; > * to express surprise that, when CakePHP is all about tests, this deficiency > has not been discovered in testing; > * to gain further input from the community before deciding this is in fact a > bug that I should write a bug report about -- 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
