xquery4 1.7.0
See the version list below for details.
dotnet tool install --global xquery4 --version 1.7.0
dotnet new tool-manifest
dotnet tool install --local xquery4 --version 1.7.0
#tool dotnet:?package=xquery4&version=1.7.0
nuke :add-package xquery4 --version 1.7.0
xquery
Command-line XQuery 3.1/4.0 processor for .NET. Query XML documents from the terminal using the PhoenixmlDb XQuery engine.
Installation
dotnet tool install -g xquery4
Usage
# Query an XML file
xquery '//book/title' library.xml
# Count elements
xquery 'count(//item)' catalog.xml
# Read from a query file
xquery -f transform.xq input.xml
# Query a directory of XML files
xquery 'collection()//product[price > 50]' ./data/
# JSON output
xquery -o json 'map { "count": count(//item) }' data.xml
# Read from stdin
cat data.xml | xquery '//item/@name'
# Show execution plan
xquery --plan 'for $x in 1 to 10 return $x * $x'
# Show timing breakdown
xquery --timing '//item' large-catalog.xml
Features
- XQuery 3.1/4.0 — FLWOR, maps/arrays, higher-order functions, string constructors
- Multiple output methods — adaptive, XML, text, JSON
- Context item — input XML is available as
.(standard XQuery) - Multiple sources — files, directories, URLs, stdin
- Full prolog support — namespaces, variable/function declarations, serialization options
- Execution plans — inspect how queries are compiled and optimized
- Timing — built-in performance profiling
Documentation
Full documentation at phoenixml.dev
License
Apache-2.0
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
This package has no dependencies.
| Version | Downloads | Last Updated |
|---|---|---|
| 2.0.0 | 0 | 9/15/2026 |
| 1.8.0 | 57 | 9/14/2026 |
| 1.7.0 | 66 | 9/11/2026 |
| 1.6.15 | 64 | 9/9/2026 |
| 1.6.14 | 84 | 9/7/2026 |
| 1.6.13 | 71 | 9/4/2026 |
| 1.6.12 | 67 | 9/1/2026 |
| 1.6.11 | 79 | 8/29/2026 |
| 1.6.10 | 79 | 8/29/2026 |
| 1.6.9 | 73 | 8/27/2026 |
| 1.6.8 | 71 | 8/26/2026 |
| 1.6.7 | 78 | 8/24/2026 |
| 1.6.6 | 78 | 8/23/2026 |
| 1.6.5 | 81 | 8/21/2026 |
| 1.6.2 | 89 | 8/16/2026 |
| 1.6.1 | 85 | 7/31/2026 |
| 1.6.0 | 90 | 7/27/2026 |
| 1.5.5 | 99 | 7/12/2026 |
| 1.5.4 | 88 | 7/9/2026 |
| 1.5.3 | 90 | 7/8/2026 |
Minor rather than patch: an element or document constructor without a node builder now raises
instead of returning something of the wrong kind, which is observable behaviour for any host
supplying its own node store.
Takes PhoenixmlDb.Core 1.7.0.
### Fixed
- **`fn:sum` returned 0 for `xs:integer` values cast from text.** `xs:integer` is unbounded, so
casting text to it yields a `BigInteger` even for a value as small as 10. The accumulation chain
matched `int`/`long`, `double`, `float`, `decimal`, untypedAtomic and the durations — but not
`BigInteger` — so such items fell through the whole chain, still counted, and contributed
nothing. `sum((xs:integer("10"), xs:integer("30")))` returned **0**, with no error.
Only `xs:integer` cast from TEXT is affected, which is what any query summing element content
produces. `fn:avg` and `fn:min`/`fn:max` already carried the case. **Present in every published
1.6.x.**
- **`fn:sum`/`avg`/`max`/`min` atomized storage-backed elements to `""`**, so aggregates over
nodes read from a store failed the cast to `xs:double` while `fn:data()` over the same nodes
returned the values. Root cause was in Core and is fixed there in 1.7.0; this is the
engine-side half.
- **Element and document constructors degraded silently without an `INodeBuilder`.** An element
constructor returned an `xs:string` of its own serialized markup; a document constructor
dropped its wrapper. Neither has a correct result available, so the substitute surfaced later
as an unrelated error — "axis step used when the context item is not a node" — pointing at the
path expression rather than the node store. Both now raise, naming `INodeBuilder` and the type
the host supplied.
### Verified
- XQuery unit suite 1554/1554
- Full W3C XSLT 3.0 sweep through the downstream engine: no set regressed
- Independently measured against an LMDB store by the phoenixml database repo: 73 pass/13 fail →
**85/1**, and a same-machine A/B against 1.6.9 across 434 QT3 test-sets at **ratio 0.989** with
no outcome changes
### Known, not fixed
`map:put` and `map:remove` copy the whole map, so building or updating a map in a loop is O(n²)
— phoenixmldb-xquery#6. Present in 1.6.x as well; the A/B above measured the one affected test
set ~21% slower on this version, a worsening of an existing quadratic rather than a new defect.
The fix is a persistent map structure and is deliberately not rushed into this release.
### Note on release discipline
16 versions shipped in the 1.6.x line of the sibling XSLT package and 14 here, several carrying
defects found only later — including the `fn:sum` bug above. See
`phoenixmldb-xslt/docs/RELEASE-HYGIENE.md`.