xquery4 1.6.9
dotnet tool install --global xquery4 --version 1.6.9
dotnet new tool-manifest
dotnet tool install --local xquery4 --version 1.6.9
#tool dotnet:?package=xquery4&version=1.6.9
nuke :add-package xquery4 --version 1.6.9
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.6.9 | 0 | 8/27/2026 |
| 1.6.8 | 37 | 8/26/2026 |
| 1.6.7 | 59 | 8/24/2026 |
| 1.6.6 | 64 | 8/23/2026 |
| 1.6.5 | 61 | 8/21/2026 |
| 1.6.2 | 78 | 8/16/2026 |
| 1.6.1 | 72 | 7/31/2026 |
| 1.6.0 | 82 | 7/27/2026 |
| 1.5.5 | 90 | 7/12/2026 |
| 1.5.4 | 79 | 7/9/2026 |
| 1.5.3 | 81 | 7/8/2026 |
| 1.5.2 | 80 | 7/7/2026 |
| 1.5.1 | 94 | 6/30/2026 |
| 1.5.0 | 80 | 6/28/2026 |
| 1.4.7 | 87 | 6/25/2026 |
| 1.4.6 | 96 | 6/17/2026 |
| 1.4.5 | 91 | 6/17/2026 |
| 1.4.4 | 86 | 6/14/2026 |
| 1.4.3 | 88 | 6/10/2026 |
| 1.4.2 | 88 | 6/6/2026 |
One fix, from Martin Honnen's testing, plus the wrong error code it was hiding.
### `format-dateTime`, `format-date` and `format-time` cast xs:untypedAtomic
format-dateTime(@date, '[D] [MNn] [Y] at [H01]:[m01]')
-> XPTY0004: Expected xs:dateTime, got XsUntypedAtomic
`@date` is an ordinary untyped attribute holding a dateTime. Function conversion rules
(XPath 3.1 §3.1.5.2) CAST xs:untypedAtomic to the declared parameter type, so this is the
ordinary case, not an edge one — Saxon formats it.
Atomizing a node yields `xs:untypedAtomic`, never `xs:string`, so the argument handling had an
arm for string and none for untypedAtomic and every untyped node argument fell through to the
type error. Six sites: `format-date`, `format-dateTime` and `format-time`, each in the 2- and
5-argument arities.
A scan for the same shape found fourteen candidate sites. Only these six are fixed; the other
eight are a cast path where untypedAtomic is unwrapped upstream, and every probe of
`xs:dateTime(@a)` / `xs:date(...)` / `xs:duration(...)` already passed. Sites that cannot be
demonstrated broken are left alone.
### Invalid lexical forms raise FORG0001
Fixing the type error exposed a second fault beneath it. `format-time($dateTimeValue, ...)`
SHOULD fail — a dateTime lexical form is not a valid `xs:time` — but the parse threw a raw
.NET `FormatException` carrying no error code instead of `FORG0001`. Pre-existing, and
unreachable until untyped values started arriving at the parse.
XQuery.Tests 1506 passed, 0 failed (1497 at 1.6.8)