Debugging is twice as hard as writing the code in the first place.
Therefore,
if you write the code as cleverly as possible, you are, by definition,
not
smart enough to debug it.
except is used when you want to use part of a relation but not
necessarily the whole thing. It’s not always useful in application code,
but when dealing with generic relations it can be really useful:
Here, except is used to remove parts of the relation that exists?
doesn’t want to use.
–Matt J.
Very useful example. Does it mean, we can use it also scope or on default
scope ? Will it be a good choice although to use scope relation if it
fits any
query, with some tailoring using except ?
–
Regards,
Arup R.
Debugging is twice as hard as writing the code in the first place.
Therefore,
if you write the code as cleverly as possible, you are, by definition,
not
smart enough to debug it.
On Sunday, 6 July 2014 13:29:15 UTC-5, Arup R. wrote:
doesn’t want to use.
–Matt J.
Very useful example. Does it mean, we can use it also scope or on default
scope ? Will it be a good choice although to use scope relation if it
fits any
query, with some tailoring using except ?
Yep. There are also some related methods; rewhere, reorder, and unscope. They allow somewhat finer control than except.
–Matt J.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.