> Well, if the column will hold numbers sure there is an advantage. You
> can perform arithmetic and numeric comparisons. You can sort based on
> the natural order of numbers, not based on lexicographical order.
Yeah, that's true enough.
I'll get it changed as I want to do everything properly.
Jim Burgess wrote:
> Thanks for your reply
>
>> Looks like a case for allow_nil:
>>
>> validates_numericality_of :children, :allow_nil => true
>
> I created the field 'children' as a string (can't remember why, perhaps
> because someone might enter 'none'??), so that doesn't work.
>
> Is ther
Thanks for your reply
> Looks like a case for allow_nil:
>
> validates_numericality_of :children, :allow_nil => true
I created the field 'children' as a string (can't remember why, perhaps
because someone might enter 'none'??), so that doesn't work.
Is there any big advantage to changing the
Jim Burgess wrote:
>
>> you can even shorten that to
>>
>> validates_numericality_of :children, :if => Proc.new { |applicant|
>> applicant.children !="" }
>>
>
Looks like a case for allow_nil:
validates_numericality_of :children, :allow_nil => true
The documentation at
http://ar.rubyonrails
> you can even shorten that to
>
> validates_numericality_of :children, :if => Proc.new { |applicant|
> applicant.children !="" }
>
Cool!
Thanks a lot.
--
Posted via http://www.ruby-forum.com/.
--~--~-~--~~~---~--~~
You received this message because you are su
On 15 May 2009, at 10:24, Jim Burgess wrote:
>
> Wow, that's very cool.
> I changed the line to:
>
> validates_numericality_of :children, :if => Proc.new { |applicant|
> true
> if applicant.children !="" }
you can even shorten that to
validates_numericality_of :children, :if => Proc.new { |a
Wow, that's very cool.
I changed the line to:
validates_numericality_of :children, :if => Proc.new { |applicant| true
if applicant.children !="" }
and that does exactly what I want.
Thanks for your time and help, Fred.
--
Posted via http://www.ruby-forum.com/.
--~--~-~--~~---
On May 15, 9:15 am, Jim Burgess
wrote:
> Hi,
>
> Is it possible to use standard validation methods in custom validation
> methods?
> eg:
>
> def check_children
> if children != ""
> validates_numericality_of :children
> end
> end
>
> When I run this code I get a no method error:
>
> und
8 matches
Mail list logo