```ruby
class Profile < ActiveRecord::Base
  validates_presence_of :name
  validate :only_one_server_for_exclusives

  has_many :excludes, :dependent => :destroy
  has_many :includes, :dependent => :destroy
  has_many :splits, :dependent => :destroy
  has_many :profilizations, :dependent => :destroy
  has_many :servers, :through => :profilizations

  named_scope :public, :conditions => { :exclusive => false }
  named_scope :public_plus, lambda { |*profilename|
    {:conditions => "exclusive = false or name = '#{profilename}'" }
  }

  accepts_nested_attributes_for :includes, :allow_destroy => true
  accepts_nested_attributes_for :excludes, :allow_destroy => true
  accepts_nested_attributes_for :splits, :allow_destroy => true

  def only_one_server_for_exclusives
    errors.add_to_base("can only have one server") if exclusive && servers.length > 1
  end
end
```

Change condition syntax to make sure ActiveRecord gets to handle the implementation details of "false". Unbreaks sqlite3 in development mode.
user
```ruby
class Profile < ActiveRecord::Base
  validates_presence_of :name
  validate :only_one_server_for_exclusives

  has_many :excludes, :dependent => :destroy
  has_many :includes, :dependent => :destroy
  has_many :splits, :dependent => :destroy
  has_many :profilizations, :dependent => :destroy
  has_many :servers, :through => :profilizations

  named_scope :public, :conditions => { :exclusive => false }
  named_scope :public_plus, lambda { |*profilename|
    {:conditions => ["exclusive = ? or name = ?", false, profilename] }
  }

  accepts_nested_attributes_for :includes, :allow_destroy => true
  accepts_nested_attributes_for :excludes, :allow_destroy => true
  accepts_nested_attributes_for :splits, :allow_destroy => true

  def only_one_server_for_exclusives
    errors.add_to_base("can only have one server") if exclusive && servers.length > 1
  end
end
```
assistant