[Felk]

Can someone explain to me what the main differences to jq are, besides the syntax?

[bonzini]

jq seems to have more focus on the generator and pipe abstractions. In jq you say "foo | map(bar)"; foo and map(bar) are both generators, and bar refers to each element of foo as ".". Here you say "for $x in foo return bar"; foo and bar are both JSON objects, and bar refers to each element of foo as "$x", so the iteration is more explicit.

Likewise, compare "sum($element.response_time)" with "map(.response_time) | add" in jq. Processing in JSONiq goes inside to outside while jq goes left to right.

[EdwardDiego]

My first thought also - would be a good entry for a FAQ or blog post.

[masklinn]

Jq is xpath, this looks to be xquery. In fact it specifically works as an xquery embed.

[bonzini]

You can write the example below in jq as

    def avg: add / length;
    group_by(.url) | map({
      "url": .[0].url,
      "hits": length, 
      "avg": map(.response_time) | avg
    })

so jq should be (at least roughly) as powerful as JSONiq.

[emmanueloga_]

... although, it seems neither JSONIq nor jq contain a "parent" operator, as far as I can tell.

[Deukhoofd]

For one thing, modifying data I guess.

[jolmg]

What do you mean? jq can modify data:

  $ jq '.foo += 1' <<< '{"foo": 2}'
  {
    "foo": 3
  }

[baq]

looks nothing like jq

  1. let $stats := collection("stats")
  2. for $access in $stats
  3. group by $url := $access.url
  4. return 
  5. {
  6.   "url": $url,
  7.   "avg": avg($access.response_time),
  8.   "hits": count($access)
  9. }

[keymone]

> besides the syntax