xquery4 1.6.10
See the version list below for details.
dotnet tool install --global xquery4 --version 1.6.10
dotnet new tool-manifest
dotnet tool install --local xquery4 --version 1.6.10
#tool dotnet:?package=xquery4&version=1.6.10
nuke :add-package xquery4 --version 1.6.10
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.1.0 | 0 | 9/17/2026 |
| 2.0.0 | 51 | 9/15/2026 |
| 1.8.0 | 63 | 9/14/2026 |
| 1.7.0 | 67 | 9/11/2026 |
| 1.6.15 | 69 | 9/9/2026 |
| 1.6.14 | 84 | 9/7/2026 |
| 1.6.13 | 71 | 9/4/2026 |
| 1.6.12 | 69 | 9/1/2026 |
| 1.6.11 | 80 | 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 | 80 | 8/24/2026 |
| 1.6.6 | 78 | 8/23/2026 |
| 1.6.5 | 81 | 8/21/2026 |
| 1.6.2 | 91 | 8/16/2026 |
| 1.6.1 | 85 | 7/31/2026 |
| 1.6.0 | 90 | 7/27/2026 |
| 1.5.5 | 100 | 7/12/2026 |
| 1.5.4 | 90 | 7/9/2026 |
No engine changes. This release exists to deliver an XSLT fix that the `xquery` tool could not
otherwise reach.
### The bundled XSLT engine was four releases stale
`PhoenixmlDb.XQuery.Cli` provides `fn:transform` by embedding `PhoenixmlDb.Xslt`, and that
reference was pinned at **1.6.6**. So `xquery 1.6.9` carried a 1.6.6 engine, and fixes released
in Xslt 1.6.7 through 1.6.10 were invisible from the command line however current the XQuery
version looked.
Martin Honnen diagnosed this from the outside: nodes returned from `fn:transform` still lost
their ancestors under `xquery 1.6.9`, months after the fix, because the fix was in Xslt 1.6.10.
He asked directly whether an XQuery release consuming it was needed. It was.
doc('sample2.xml') -> transform(...) -> $result/path()
was: /Q{}book[1] /Q{}book[1]
now: /Q{}books[1]/Q{}book[1] /Q{}books[1]/Q{}book[2]
Pinned to Xslt 1.6.10, which also brings: `document-node(element(x:report))` matching, typed
templates keeping a copied attribute's tree, W3C error codes carrying an ErrorCode and
location, and the CLI reporting errors instead of crash-dumping over them.
**A version number describes the package, not what it bundles.** Nothing in `xquery --version`
told Martin which XSLT engine he had. That is a packaging hazard worth naming, not just a stale
pin: the two versions can drift arbitrarily far apart and nothing surfaces it.
XQuery.Tests 1506 passed, 0 failed — unchanged; this is a dependency bump