PhoenixmlDb.XQuery 1.6.10

.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.10
                    


                    

                
NuGet\Install-Package PhoenixmlDb.XQuery -Version 1.6.10
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.10" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="PhoenixmlDb.XQuery" Version="1.6.10" />
                    


                            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.10
                    


                    

                
#r "nuget: PhoenixmlDb.XQuery, 1.6.10"
#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.10
#: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.10
                    


                            Install as a Cake Addin
                        

                    

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


                            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.11 44 8/29/2026
1.6.10 77 8/29/2026
1.6.9 90 8/27/2026
1.6.8 95 8/26/2026
1.6.7 142 8/24/2026
1.6.6 138 8/23/2026
1.6.5 134 8/21/2026
1.6.2 173 8/16/2026
1.6.1 186 7/31/2026
1.6.0 159 7/27/2026
1.5.5 188 7/12/2026
1.5.4 187 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 185 6/14/2026
Loading failed

No engine changes. This release exists to deliver an XSLT fix that the `xquery` tool could not
otherwise reach.

### The bundled XSLT engine was four releases stale

`PhoenixmlDb.XQuery.Cli` provides `fn:transform` by embedding `PhoenixmlDb.Xslt`, and that
reference was pinned at **1.6.6**. So `xquery 1.6.9` carried a 1.6.6 engine, and fixes released
in Xslt 1.6.7 through 1.6.10 were invisible from the command line however current the XQuery
version looked.

Martin Honnen diagnosed this from the outside: nodes returned from `fn:transform` still lost
their ancestors under `xquery 1.6.9`, months after the fix, because the fix was in Xslt 1.6.10.
He asked directly whether an XQuery release consuming it was needed. It was.

   doc('sample2.xml') -> transform(...) -> $result/path()

   was: /Q{}book[1]              /Q{}book[1]
   now: /Q{}books[1]/Q{}book[1]  /Q{}books[1]/Q{}book[2]

Pinned to Xslt 1.6.10, which also brings: `document-node(element(x:report))` matching, typed
templates keeping a copied attribute's tree, W3C error codes carrying an ErrorCode and
location, and the CLI reporting errors instead of crash-dumping over them.

**A version number describes the package, not what it bundles.** Nothing in `xquery --version`
told Martin which XSLT engine he had. That is a packaging hazard worth naming, not just a stale
pin: the two versions can drift arbitrarily far apart and nothing surfaces it.

   XQuery.Tests 1506 passed, 0 failed — unchanged; this is a dependency bump