If you are adding ActiveRecord::Relation objects to get an 'OR' result rather than 'AND' (you'd get 'AND' behavior by chaining), and you still need the result to be an ActiveRecord::Relation to play nice with some other code (meta_search, for example)....
def matching_one_or_two
temp = Model.matching_one + Model.matching_two
Model.where('id in (?)',temp.map(&:id))
end
Certainly not the world's greatest performance, but it results in an ActiveRecord::Relation object pointing at the 'OR' results.
You can also just put the "OR" directly into the sql, rather than asking Rails to generate it for you, to give your database application a chance to perform better. One example:
Model.where("table_name.col = 'one' OR table_name.col = 'two'")
That will also return an ActiveRecord::Relation object.