pepe wrote in post #962574: > I believe your problems are coming from the fact that you allow > something different than true/false in your DB column. If the column > is supposed to contain a boolean value, why are you allowing it to > contain the null value? A boolean value is either true or false, not > null.
Poppycock. It's perfectly OK to have Boolean columns (or any columns) be null-capable if the semantics of the data dictate that. Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
