[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Match/Context naming
- From: Thomas Hallgren <thomas@xxxxxxx>
- Date: Wed, 24 Feb 2010 08:28:42 +0100
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:188.8.131.52) Gecko/20100120 Fedora/3.0.1-1.fc12 Lightning/1.0b1 Thunderbird/3.0.1
On 02/24/2010 12:28 AM, Susan Franklin McCourt wrote:
I have problems with the term 'match' since I consider all queries to be
a filter that produce a result of instances that 'match'. Susan's
suggestion also shows this by adding the term to both queries. I think
the term itself thus becomes redundant. It doesn't help bringing clarity
into what it is that differentiates the two types.
To me, the term 'relative' suggests that the other query is 'absolute'
or perhaps 'concrete' which in turn seems a bit far fetched.
On 02/24/2010 03:33 AM, Simon Kaegi wrote:
An aggregation to me is something that brings several things together
into one thing. Our 'context' expression is applied on a collection and
produces a subset of that collection. Can that be called an aggregation?
In SQL we have the various aggregate functions.
Our 'match' query can always be turned into a 'context' query using the
<match each> -> everything.select(each | <match each>)
Perhaps I'm too focused on the expression aspect but I'd like the names
to be explanatory so that the user intuitively knows which one to pick
for the purpose at hand. Here's another suggestion: