Unify unique and unique_index property options
Reported by Dan Kubb | June 20th, 2008 @ 03:10 AM | in 1.x
Currently you pass in a :unique and :unique_index options when declaring properties. The :unique option sets up validation on the property, while the :unique_index sets up the actual unique indexes when using auto_migrate!
I think that :unique_index should be deprecated and the functionality should be rolled into :unique. It makes no sense to use one and not the other as far as I can tell. In fact it could be confusing if you specified :unique_index and forget :unique, and then get DB errors.
Comments and changes to this ticket
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 »
Sam Smoot