Bitfield not being set when all bits are 0 about bitfields HOT 5 CLOSED

is User.new.email_preferences == 0 ?

if not, change_column :users, :email_preferences, :integer, :default => 0, :null => false

from bitfields.

Thanks for responding @grosser.

Setting the db column default to 0 allows the above spec to pass, but it causes this spec to fail:

  describe "set_email_prefs_to_defaults" do
    it "should set the email preferences to the defaults on create" do
      user = Factory(:user)
      user.credits_email.should == true
      user.weekly_results_email.should == true
      user.challenges_email.should == true
      user.jackpot_results_email.should == true
    end
  end

because attribute_present?(:email_preferences) in my previous set_email_prefs_to_defaults method returns true due to the db column default.

I did, however, find a nice solution that allows both specs to pass:

class User < ActiveRecord::Base
  ...
  after_initialize :set_email_prefs_to_defaults
  ...
  def set_email_prefs_to_defaults
    self.credits_email ||= true
    self.weekly_results_email ||= true
    self.challenges_email ||= true
    self.jackpot_results_email ||= true
  end
end

from bitfields.

setting bitfield columns before create / initialize is a complicated topic,
but i think you almost nailed it, try before_initialize, then even

User.new(:credits_email=>false).credits_email.should == false

from bitfields.

There is no before_initialize ...
I added a spec for how it should work, but so far its failing, maybe you can find a way to fix it :)
2170dc5

from bitfields.

closing this, doing false ||= true is true ... no bug here ...

from bitfields.