Me :) https://github.com/rails/rails/pull/7072
On Monday, July 16, 2012 3:36:39 PM UTC-4, Jon Leighton wrote: > > >> I'm hoping there is a better way to deal with this problem, either with > a > >> less hacky ARel approach or something different all together. > > > > It seems like we should be using the underlying database value (the > > attribute value rather than the return value of the method call) for the > > unique constraint. I think this might be a bug. Jon, wdyt? > > Yes, I agree. Who wants to create a patch? :) > > -- > http://jonathanleighton.com/ > > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/sY4OrKfqp94J. 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.
