validates_uniqueness_of is case_sensitive by default
Reported by Trotter Cashion | August 22nd, 2008 @ 03:33 PM | in 2.1.2
The ActiveRecord docs claim that validates_uniqueness of is case_insensitive by default, but the code claims that it is case sensitive. See this paste from Rails 2.1 to see what I'm talking about. The bug also exists in edge.
I would prefer that validates_uniqueness_of is case_insensitive by default. I'll make a patch w/ test when I have time.
Comments and changes to this ticket
-
José Valim August 23rd, 2008 @ 04:33 PM
I think the default should be the same as the database default.
MySQL, for example, is case insensitive. I don't know if all are case insensitive.
-
Peter Wagenet August 23rd, 2008 @ 06:11 PM
As it is, it seems that either the docs or the method need to be changed.
-
Tarmo Tänav September 18th, 2008 @ 07:11 AM
- → Tag changed from “activerecord bug edge” to “activerecord bug edge”
- → Milestone changed from “2.x” to “2.1.1”
It is intended to be case sensitive by default, there is an explicit commit that says so, but somehow during a documentation mass-update in http://github.com/rails/rails/co... it got flipped to false (still correct in edge though).
-
Tarmo Tänav September 18th, 2008 @ 07:12 AM
- → Milestone changed from “2.1.1” to “2.1.2”
-
Tarmo Tänav September 18th, 2008 @ 10:21 PM
- → State changed from “new” to “resolved”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
Repository is at http://github.com/rails/rails
Check out the development master (Edge Rails):
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too"..
