xquery4 1.6.9

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
Additional Details

these previous versions should be considered unusabl e due to the lack of proper parser implementation features. Versions 2.0 and above are a closer match to the standards.

There is a newer version of this package available.
See the version list below for details. 
dotnet tool install --global xquery4 --version 1.6.9
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.9
This package contains a .NET tool you can call from the shell/command line. 
#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 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.

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)