DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26413>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26413 Indexed Field Date Validation Allows Invalid Dates [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | Version|1.1 Final |Nightly Build ------- Additional Comments From [EMAIL PROTECTED] 2004-02-11 14:51 ------- Sorry I didn't get back to you earlier. I have now tried this using the nightly build from 10th Feb 20004 and the problem is still exists. In fact this problem occurs in all the FieldChecks validations that return null if the value is null. From looking at the source validateByte(), validateShort (), validateInteger(), validateLong(), validateFloat(), validateDouble() and validateCreditCard() are all affected by the same issue. I tried it out for the integer validation and it didn't work properly either for indexed fields. I think the best solution is for all these methods to just return a boolean rather than the value they are validating - and return 'true' (i.e. valid) if the value is blank or null. What do you think - if I do a patch on this basis would you be willing to commit it? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
