Unify unique and unique_index property options
Reported by Dan Kubb (dkubb) | June 20th, 2008 @ 03:10 AM
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
-
Jonathan Stott (namelessjon) November 30th, 2008 @ 07:59 AM
- Tag set to “dm-core, property, suggestion”
- Milestone cleared.
- State changed from “new” to “open”
- Assigned user changed from “Sam Smoot” to “Dan Kubb (dkubb)”
-
Dan Kubb (dkubb) December 4th, 2008 @ 02:53 AM
- State changed from “open” to “not-applicable”
Even though this is my own ticket, it's a suggestion and probably not best suited for keeping it hidden away in LH.
Marking this as not-applicable, but it will be updated in dkubb/dm-core to work like this.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Dan Kubb (dkubb)