xquery4 1.6.5

There is a newer version of this package available.
See the version list below for details.
dotnet tool install --global xquery4 --version 1.6.5
                    
This package contains a .NET tool you can call from the shell/command line.
dotnet new tool-manifest
                    
if you are setting up this repo
dotnet tool install --local xquery4 --version 1.6.5
                    
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=xquery4&version=1.6.5
                    
nuke :add-package xquery4 --version 1.6.5
                    

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 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

Version Downloads Last Updated
1.6.8 0 8/26/2026
1.6.7 55 8/24/2026
1.6.6 63 8/23/2026
1.6.5 60 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
1.4.1 96 6/4/2026
Loading failed

### Fixes

- **`fn:json-doc` resolves a registered resource URI even without a static base URI.** The
 translation from a host-registered resource URI to its backing file sat inside a
 `StaticBaseUri != null` guard, alongside the unrelated job of rebasing a *relative* URI.
 Those are different concerns: a registered URI is normally already absolute, so it needs no
 rebasing but does need mapping. A host that registered resources without also setting a base
 URI got no mapping at all, and `json-doc` then treated the URI as a literal path —
 `Could not find a part of the path '…/bin/Debug/net10.0/http:'`. The two-argument overload
 never mapped at all, so `json-doc($uri)` and `json-doc($uri, $options)` disagreed about
 whether a registered URI resolves. Found via the W3C QT3 suite, whose `<resource>`
 declarations bind logical `http://` URIs to local files.

### Version alignment

From 1.6.5 the engine libraries and the CLI tools built on them share a single version, so a
matching number means a compatible set. See `PhoenixmlDb.Core` 1.6.5 for the rationale.

One documented exception: `PhoenixmlDb.XQuery.Cli` still embeds **XSLT 1.6.4**. The CLI needs
`PhoenixmlDb.Xslt`, which in turn needs `PhoenixmlDb.XQuery`, and this repo publishes its
library and CLI together — so pinning 1.6.5 would require it to exist before the package it
depends on was published. `Directory.Packages.props` carries the full explanation. The library
itself, `PhoenixmlDb.XQuery`, has no such constraint: it depends only on Core.