Thank you for the detailed explanation. It makes sense now. It's the way I
am thinking that's wrong.
Maybe a raw SQL query is better in this case. But it bothers me that I
can't think of a way to create reusable methods of sets of records.
My queries aren't that simple as "a=>1" and I want to be able to use
"Test.a" or "Test.b" and "Test.c".
You can imagine them in a real case as:
Test.cars_with_blue_color
Test.cars_with_alloy_wheels
Test.cars_that_need_service
then any of the first two can be used individually but there could be a
case that a third method can combine those three. For example:
def top_cars_to_sell
(cars_with_blue_color + cars_with_alloy_wheels) - cars_that_need_service
end
I know that it doesn't work, I am describing my case.
Something like that.
Thanks again.
--
You received this message because you are subscribed to the Google Groups
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sequel-talk.
For more options, visit https://groups.google.com/d/optout.
