Query for Action not equals

[ssimon]

Today the Action Query only support the format {"Action":"ADD"}, meaning you cannot specify Action ADD or UPDATE. Changing the query format for Action into {"Action": {"ADD":true}} would allow you to use Action:{"DELETE":false} to specify ADD or UPDATE

[laserval]

For the current design of queries, I suppose this is the way it can be implemented. But I'm not sure about the true/false design of the queries - when would you ever use both? E.g. { touched: { fix-html: true, fetch-attachments: false} }. To me it seems to only make queries more confusing.

In this case, it seems clearer to me that it would be a list of actions.

[ssimon]

I guess, but the design of the queries would at least be the same..

{
fetched: {"fix-html" : true},
exists: {"html" : true},
action: {"ADD" : true}
}

But your call.. I just want the functionality.

When we're talking about query syntax, wouldn't it be nice to be able to do
OR-queries as well..?

{
or: {
fetched: {"my-last-stage-for-adds" : true },
fetched: {"my-last-stage-for-deletes" : true },
}
}

or maybe a combination of AND and OR:

{
or: {
and : {
fetched: {"my-last-stage-for-adds" : true },
}
fetched: {"my-last-stage-for-deletes" : true },
}
}

On Wed, Aug 7, 2013 at 12:12 PM, Olof Nilsson notifications@github.comwrote:

For the current design of queries, I suppose this is the way it can be
implemented. But I'm not sure about the true/false design of the queries -
when would you ever use both? E.g. { touched: { fix-html: true,
fetch-attachments: false} }. To me it seems to only make queries more
confusing.

In this case, it seems clearer to me that it would be a list of actions.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/229#issuecomment-22241579
.

[laserval]

Oh yes, I agree with the current queries it makes the most sense to be consistent.

OR-support should absolutely be added, but I believe that requires some changes to the way queries work anyway.