views:

527

answers:

1

I have a model that has two fields, which I will call first_name and last_name, and I want to make sure that the combination of the two are case-insensitively unique. I've gotten halfway there by using this:

validates_uniqueness_of :first_name, :scope => :last_name

The problem is that the uniqueness check seems to be case sensitive, even though the documentation says it should be case insensitive by default. So given an existing record:

{ :first_name => 'John', :last_name => 'Smith' }

This will be allowed:

{ :first_name => 'JOHN', :last_name => 'SMITH' }

As well as any additional record where there is any variation of case in either the first or last name. Why are these records being allowed? How can I enforce case insensitive uniqueness across both fields together?

+1  A: 

Did you try validates_uniqueness_of :first_name, :scope => :last_name, :case_sensitive => false?

The documentation says it's true by default.

(I think the link you gave is to some outdated documentation. IIRC, the default for this did change in the last couple of years.)

Luke Francl
You're right! I was mislead by the documentation I found. Setting `:case_sensitive => false` made it work for the first_name, but it doesn't work the other direction. It will still accept `{ :first_name => 'John', :last_name => 'SMITH' }`. Is there a way to make it work bi-directionally? Would I just include two `validates_uniqueness_of` rules with the field swapped?
Jimmy Cuadra
I tried adding another validation with the two fields swapped. It will now catch cases where one of the fields is differently cased, but not if both are, so this still gets through: `{ :first_name => 'JOHN', :last_name => 'SMITH' }`.
Jimmy Cuadra
I'd just write a custom validation method at this point if I were you.
Luke Francl
Yep, that's what I ended up doing. Thanks all.
Jimmy Cuadra