On 29 Dec 2009, at 12:40, Allen Madsen wrote: > I think the problem is that there is no way to distinguish between a nil > value and a blank value coming from the request. They both look the same and > they both have their uses. I don't think your solution solves this problem, > because there are likely cases like above where blank has significance.
In the case where a column is set to :null => false then the plugin won't nullify the value. I don't know about your end users but mine wouldn't understand the difference between a nil value and an empty string - relying on them to determine what a value should be is not something I want to push on them. Also blank number fields are already converted to nil. Andrew -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
