Forum: Ruby on Rails check whether the boolean value true or false

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Dcf093a36c8a7e286dbefe10454813e1?d=identicon&s=25 Ishara Gunathilake (Guest)
on 2008-11-01 06:59
(Received via mailing list)
i have a table called "confirm_clients",there are 3columns,they are
 t.column :user_id, :string
 t.column :msg_id, :string
 t.column :confirm, :boolean

i want to check whether the boolean value of confirm is true
when a given user_id and msg_id,plz can anyone how can i do it
C5c0e0499446b84fd3bcc61cf7862539?d=identicon&s=25 Thani Ararsu (thaniyarasu)
on 2008-11-01 08:48
Ishara Gunathilake wrote:
> i have a table called "confirm_clients",there are 3columns,they are
>  t.column :user_id, :string
>  t.column :msg_id, :string
>  t.column :confirm, :boolean
>
> i want to check whether the boolean value of confirm is true
> when a given user_id and msg_id,plz can anyone how can i do it

try to use "before_save" in model class
929c5c32f7903a1154be888822c5ec20?d=identicon&s=25 mrbless (Guest)
on 2008-11-01 08:55
(Received via mailing list)
assuming 0 as false and 1 as true. Try it out
confirm_client=ConfirmClient.find(5) # I am supposing the client with
id 5
if confirm_client.confirm==1 #yes indeed this client is verified
  do_something
else #not verified client
  do_something_else probably redirect to some place with
flash[:notice]
end

On Nov 1, 10:58 am, "Ishara Gunathilake" <jaimgunathil...@gmail.com>
81b61875e41eaa58887543635d556fca?d=identicon&s=25 Frederick Cheung (Guest)
on 2008-11-01 13:53
(Received via mailing list)
On Nov 1, 7:54 am, mrbless <mrbl...@gmail.com> wrote:
> assuming 0 as false and 1 as true. Try it out
> confirm_client=ConfirmClient.find(5) # I am supposing the client with
> id 5

How true/false are represented in the DB is database dependant. You
don't need to worry about that though - confirm_client.confirm is
typecasted by rails to either true or false no matter what the
underlying column stores (t/f, 0/1, Y/N etc...)

Fred
Ef3aa7f7e577ea8cd620462724ddf73b?d=identicon&s=25 Rob Biedenharn (Guest)
on 2008-11-01 18:56
(Received via mailing list)
On Nov 1, 2008, at 8:52 AM, Frederick Cheung wrote:
> Fred
But, I've found that you almost always want to replace:
   t.column :confirm, :boolean
with
   t.column :confirm, :boolean, :default => false, :null => false

Unless you need the SQL NULL to mean something other than "not
true" (because it is also "not false")

Otherwise, something like:

   ConfirmClient.find(:all, :conditions => { :confirm => [true,
false] })

Does *NOT* find all the records.  This is usually when you begin to
question your sanity until discovering the NULL values in the
'confirm' column.

-Rob

Rob Biedenharn    http://agileconsultingllc.com
Rob@AgileConsultingLLC.com
This topic is locked and can not be replied to.