[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Match/Context naming
- From: Thomas Hallgren <thomas@xxxxxxx>
- Date: Tue, 23 Feb 2010 22:34:13 +0100
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:22.214.171.124) Gecko/20100120 Fedora/3.0.1-1.fc12 Lightning/1.0b1 Thunderbird/3.0.1
On 02/23/2010 09:56 PM, Ian Bull wrote:
I'm not a big fan of Each vs. All as it sounds like Each doesn't
include all the results.The names give a hint on what the expression is applied to. When you
author the query, you must consider if the expression is applied to
'each row' or to 'all rows'. The words Each and All are correlated, like
Min/Max, Single/Multiple, etc.
I'm not saying that Each and All are the best terms. I'm just pointing
out why I think they have some validity.
You still fit the description of being the tallest person. I.e. you
"match" that description.
Here is some background (why Jeff and I arrived at these names).
MatchQueries are queries in which you can answer an elements inclusion
by looking at the element alone. For example, is my name "Ian Bull".
I doesn't matter who else is in the room. Context queries, on the
other hand, require knowledge of all the other elements. Am I the
tallest person in the room? This obviously depends on who else is in
We broke the queries down this way because MatchQueries can be easily
done in parallel. While you might be able to do ContextQueries in
parallel, there is not general way.That sounds like an evaluator implementation concern. Valid I'm sure,
but does it bring any clarity for the user who authors a query?