Updated README regarding active record validations, fix for setting n…

…il values

README.md

@@ -243,9 +243,18 @@ setting did not receive a value yet:
 :validations => {:custom => [:must_be_42]}
 ```
 
-There are some built-in validations (see above), but you may also define custom
-validations either by passing in anonymous functions or symbols representing
-class methods either in the setting class or the assigned model.
+There are some built-in validations (see above), but they should be mostly used for globally defined
+and globally used settings (`Setting.somethingsomething`).
+For model specific settings, you may treat the setting accessors just like normal columns
+and define your validations accordingly, e.g.
+
+```ruby
+setting_accessor :my_string, :type => :string
+setting_accessor :my_number, :type => :integer
+
+validates :my_string, :presence => true
+validates :my_number, :numericality => {:only_integer => true}
+```
 
 Contributing
 ------------

lib/setting_accessors/converter.rb

@@ -5,7 +5,7 @@
 #
 # If the value cannot be parsed in the required type, +nil+ is assigned.
 # Please make sure that you specify the correct validations in settings.yml
-# to avoid this.
+# or assigned model to avoid this.
 #
 # Currently supported types:
 #   - Fixnum
@@ -27,6 +27,10 @@ def convert(new_value)
     #If the value is set to be polymorphic, we don't have to convert anything.
     return new_value if @value_type == 'polymorphic'
 
+    #ActiveRecord only converts non-nil values to their database type
+    #during assignment
+    return new_value if new_value.nil?
+
     parse_method = :"parse_#{@value_type}"
 
     if private_methods.include?(parse_method)

lib/setting_accessors/version.rb

@@ -1,3 +1,3 @@
 module SettingAccessors
-  VERSION = '0.0.2'
+  VERSION = '0.0.3'
 end