Is there anything wrong with the fact that by default for a boolean field , ActiveRecord migration is used nilinstead falsefor use with Postgres?
nil
false
I like the way it gives a small bit of extra data - regardless of whether this field is marked as true or false.
there is nothing that would prevent you from using nil in boolean - but to me personally, like my booleans, were true or false, I found that nil can lead to some ugly code