+1 for reverting this ASAP.
The reason was already very clearly explained in the 4th post of this
thread.
I believe, this is the most important point.
On Wed, Feb 16, 2011 at 8:37 PM, Will Bryant <will.bry...@gmail.com>
wrote:
> And to do it at all breaks the relational algebra idea badly.
Now, let me show you my real world tragedy.
# model
class User
scope :admin, where(:id => [1, 2, 3, 4])
end
# controller
def admin?
User.admin.where(:id => session[:user_id]).exists?
end
Imagine what happened to my app!
As for the "OR" API, I think squirrel had the best syntax against
ambiguity.
Book.written_by('david').published #=> AND
Book.or {
written_by('david')
published
} #=> OR
--
Akira Matsuda<ron...@dio.jp>
--
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 rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
