Irrespective of the argument regarding where this uniqueness constraint belongs, this feature seems like a solution for a relatively uncommon use case. As Xavier pointed out, and as Will Bryant demonstrated earlier in this thread, it's possible to implement in a few lines of code. Rails, like any framework, should focus on providing core value, not on providing sugar for every possible use case.
On Aug 1, 12:28 pm, Xavier Noria <[email protected]> wrote: > On Sat, Aug 1, 2009 at 8:33 PM, Jason King<[email protected]> wrote: > > It's a very slippery slope if the core starts trying to predict and > > protect developers from non-Rails assumptions. > > I agree. It is kind of a finder mixed with an assertion. Doesn't fit > in core in my view. It's easy to write it yourself nonetheless. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
