PhoenixmlDb.XQuery 1.6.6

.NET 8.0 This package targets .NET 8.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package PhoenixmlDb.XQuery --version 1.6.6
                    


                    

                
NuGet\Install-Package PhoenixmlDb.XQuery -Version 1.6.6
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="PhoenixmlDb.XQuery" Version="1.6.6" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="PhoenixmlDb.XQuery" Version="1.6.6" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="PhoenixmlDb.XQuery" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add PhoenixmlDb.XQuery --version 1.6.6
                    


                    

                
#r "nuget: PhoenixmlDb.XQuery, 1.6.6"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package PhoenixmlDb.XQuery@1.6.6
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=PhoenixmlDb.XQuery&version=1.6.6
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=PhoenixmlDb.XQuery&version=1.6.6
                    


                            Install as a Cake Tool

PhoenixmlDb.XQuery

XQuery 4.0 query engine for PhoenixmlDb — query XML and JSON documents with the full power of XQuery.

Features

  • Full XQuery 4.0 — FLWOR expressions, constructors, modules, user-defined functions
  • XPath 4.0 — complete XPath implementation with 240+ built-in functions
  • JSON support — json-doc(), parse-json(), maps, arrays — query JSON natively
  • Full-text search — ft:contains() with stemming, wildcards, proximity, scoring
  • Update Facility — insert, delete, replace, rename, transform expressions
  • Type system — records, enums, union types (XQuery 4.0)

Quick example

using PhoenixmlDb.XQuery.Execution;

var engine = new QueryEngine();

// Simple query
var results = engine.ExecuteToListAsync(
    "for $x in 1 to 10 where $x mod 2 = 0 return $x * $x");

// Query XML documents
var books = engine.ExecuteAsync(
    "//book[price > 30]/title",
    containerId);
Package Description
PhoenixmlDb.Core Core types and XDM data model (dependency)
PhoenixmlDb.Xslt XSLT 4.0 transformation engine
PhoenixmlDb.XQuery.Cli xquery command-line tool

Documentation

Full documentation at phoenixml.dev

License

Apache 2.0

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  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.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on PhoenixmlDb.XQuery:

Package Downloads
PhoenixmlDb.Xslt

XSLT 4.0 transformation engine for PhoenixmlDb
Phoenixml.Platform.Editor.Xml

XML/XSD vocabulary binding for Phoenixml.Platform — concrete IDocument and ITreeNodeProvider implementations against PhoenixmlDb.Core's XDM, XSD schema validation pipeline.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.6.8 0 8/26/2026
1.6.7 113 8/24/2026
1.6.6 120 8/23/2026
1.6.5 109 8/21/2026
1.6.2 169 8/16/2026
1.6.1 184 7/31/2026
1.6.0 157 7/27/2026
1.5.5 185 7/12/2026
1.5.4 185 7/9/2026
1.5.3 133 7/8/2026
1.5.2 137 7/7/2026
1.5.1 152 6/30/2026
1.5.0 114 6/28/2026
1.4.7 147 6/25/2026
1.4.6 222 6/17/2026
1.4.5 144 6/17/2026
1.4.4 184 6/14/2026
1.4.3 137 6/10/2026
1.4.2 119 6/6/2026
1.4.1 237 5/29/2026
Loading failed

Three fixes, all reported by Martin Honnen on 2026-08-22 while running XPath 4.0 examples
from the specs and from the Saxon/BaseX write-ups against this engine.

### `fn:partition` splits where the spec says to

`partition($input, $split)` called its predicate with the wrong shape and returned the whole
input as one partition, so

   partition(1 to 7, function($partition, $next) { count($partition) eq 2 }) => count()

gave 1 where Saxon gives 4. The spec's `$split` takes two arguments — the partition
accumulated so far and the next item — and is asked, for each item, whether the partition
should be closed BEFORE it. Arrays are now returned as arrays rather than flattened, which
is what made the adaptive serialization of the result look like `1234567`.

### `fn` is accepted as a synonym for `function`

XPath/XQuery 4.0 §4.6.6: "The keywords function and fn are synonymous."

   fn($x, $y) { $x + $y }

The 4.0 specs and their promotional examples use the short form throughout, so those
examples could not previously be run against this engine unchanged — which is the point of
them.

`fn` is also the standard namespace prefix, so a bare keyword token would have stopped
`fn:count(…)` lexing as a prefixed name and broken every call in the standard namespace.
`KW_FN` is added to the parser's `ncName` rule, which is how this grammar already handles
its other contextual keywords.

NOT implemented, deliberately: the no-parens focus-function form `fn { @vat + @price }`
from §4.6.6.1, which binds its argument to the context value rather than a named parameter.
The AST has no context-binding concept, and treating it as a zero-arity function would be
silently wrong rather than merely missing. It remains a parse error.

### `fn:parse-html` fails loudly instead of returning escaped input

`parse-html` tried the input as XML and, when that failed, escaped the whole string into
`<html><body>` and returned it — so a caller got a plausible-looking document whose body was
the literal source text.

This does not implement HTML parsing. Real HTML needs an HTML5 tokenizer and tree builder
(implied end tags, void elements, implicit head/body), which this engine does not have and
.NET does not provide. It replaces a silent wrong answer with `FODC0006` and a message
saying why, so the limitation is discovered at the call rather than downstream. Well-formed
XHTML still parses through the XML path, unchanged.

Implementing it properly is a dependency decision (AngleSharp or similar) and is left open.

### Notes

`PhoenixmlDb.Core` is republished at 1.6.6 unchanged, under the uniform-version policy —
see its 1.6.5 notes.

The `xquery` tool embeds the XSLT engine from the previous release (1.6.5 in this train).
The CLI needs `PhoenixmlDb.Xslt` for `fn:transform`, and `PhoenixmlDb.Xslt` needs
`PhoenixmlDb.XQuery`, so the tool cannot ship against an Xslt build that does not exist yet.
The library itself depends only on Core and has no such lag.