PhoenixmlDb.XQuery 2.4.1

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


                    

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


                            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 2.4.1
                    


                    

                
#r "nuget: PhoenixmlDb.XQuery, 2.4.1"
#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@2.4.1
#: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=2.4.1
                    


                            Install as a Cake Addin
                        

                    

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


                            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 — contains text 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
2.8.0 67 10/9/2026
2.7.0 103 10/7/2026
2.6.0 138 10/6/2026
2.5.1 360 10/1/2026
2.5.0 94 10/1/2026
2.4.1 406 9/28/2026
2.4.0 138 9/28/2026
2.3.0 126 9/28/2026
2.2.0 187 9/24/2026
2.1.0 333 9/17/2026
2.0.0 356 9/15/2026
1.8.0 299 9/14/2026
1.7.0 685 9/11/2026
1.6.15 206 9/9/2026
1.6.14 194 9/7/2026
1.6.13 158 9/4/2026
1.6.12 182 9/1/2026
1.6.11 154 8/29/2026
1.6.10 177 8/29/2026
1.6.9 251 8/27/2026
Loading failed

A patch for a regression in 2.4.0 that **broke XSpec compilation** (phoenixmldb-xslt#191, reported
by Martin Honnen two hours after 2.4.0 shipped).

### Fixed

**A string subtype had no effective boolean value.** `if (xs:NCName('a'))` raised `FORG0006`
instead of returning true. The spec says a value of type `xs:string` or anything derived from it is
true when non-empty. This hole predates 2.4.0, but it was unreachable in practice until 2.4.0
correctly made `fn:prefix-from-QName` return `xs:NCName` (and `fn:default-language` return
`xs:language`). XSpec's compiler tests a prefix in an `if`, so every XSpec suite stopped compiling.

The same sweep found three other places that switched on runtime type with no string-subtype case:

- **Map keys.** An `xs:NCName` key and an equal `xs:string` were different keys, so lookups missed
 and merges kept duplicates.
- **`fn:translate`** rejected a string subtype with `XPTY0004`.
- **`fn:collation-key`** (both arities) rejected it too.

49 operations on subtype values were checked in all; the rest were already correct.

### Conformance

Per-case QT3 diff against 2.4.0: **no changes**. Neither suite has a case for these shapes, which
is why the regression shipped. XSpec compilation now gates every release.