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 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.
