xquery4 1.3.12
See the version list below for details.
dotnet tool install --global xquery4 --version 1.3.12
dotnet new tool-manifest
dotnet tool install --local xquery4 --version 1.3.12
#tool dotnet:?package=xquery4&version=1.3.12
nuke :add-package xquery4 --version 1.3.12
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 |
|---|---|---|
| 1.3.15 | 60 | 5/22/2026 |
| 1.3.14 | 49 | 5/21/2026 |
| 1.3.13 | 56 | 5/20/2026 |
| 1.3.12 | 66 | 5/19/2026 |
| 1.3.11 | 65 | 5/18/2026 |
| 1.3.10 | 61 | 5/17/2026 |
| 1.3.9 | 54 | 5/15/2026 |
| 1.3.7 | 60 | 5/14/2026 |
| 1.3.6 | 55 | 5/13/2026 |
| 1.3.5 | 58 | 5/13/2026 |
| 1.3.4 | 65 | 5/12/2026 |
| 1.3.3.1 | 49 | 5/12/2026 |
| 1.3.3 | 64 | 5/11/2026 |
| 1.3.2 | 64 | 5/9/2026 |
| 1.3.1 | 64 | 5/8/2026 |
| 1.3.0 | 53 | 5/8/2026 |
| 1.2.5.1 | 64 | 5/7/2026 |
| 1.2.5 | 53 | 5/6/2026 |
| 1.2.4 | 52 | 5/6/2026 |
| 1.2.3 | 49 | 5/6/2026 |
Namespace ID collision in XdmDocumentStore: skip already-claimed IDs and mirror new bindings into the reverse map so element constructors with multiple xmlns: declarations serialize each prefix to its correct URI (Martin Honnen Schematron repro).
InMemoryUpdatableNodeStore now starts dynamic IDs at FirstUserNamespaceId (100) instead of 3 — old value collided with reserved IDs Xsd=3..Xslt=10 on the 8th interned URI.
CLI: -p/--param/-p:name=value binds external variables; --timing now also prints peak working set and total managed allocations.
External variable binding casts CLI-supplied strings to declared atomic types (Saxon semantics) so `declare variable $n as xs:integer external` works with `-p n=10`.
See RELEASES.md for full notes.