# Validates\_uniqueness\_of customization

**URL:** <https://www.ruby-forum.com/t/validates-uniqueness-of-customization/127246>\
**Category:** Rails\
**Created:** [January 26, 2008, 11:57pm UTC](https://www.ruby-forum.com/t/validates-uniqueness-of-customization/127246 "2008-01-26T23:57:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dcgrigsby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/b5e925/32.png) [@dcgrigsby](https://www.ruby-forum.com/u/dcgrigsby)\
**Post date:** [January 26, 2008, 11:57pm UTC](https://www.ruby-forum.com/t/validates-uniqueness-of-customization/127246/1 "2008-01-26T23:57:41Z")

</div>

Hey,

I have a simple web app where I would like users to sign up with a  
maximum of two accounts per email address. What would be the rails way  
of accomplishing this. Is there anyway of modifying  
validates\_uniqueness\_of to perform the proper validations?

Thanks

---

<div class="post-metadata">

**Author:** ![dcgrigsby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/b5e925/32.png) [@dcgrigsby](https://www.ruby-forum.com/u/dcgrigsby)\
**Post date:** [January 28, 2008, 4:53am UTC](https://www.ruby-forum.com/t/validates-uniqueness-of-customization/127246/2 "2008-01-28T04:53:10Z")

</div>

why do you insist on validates\_uniquesness\_of?  
you can just use a normal, customized validate method.  
but if you insist, you can redefine that method.

On Jan 27, 6:57 am, Dan G. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)