PhoenixmlDb.XQuery 1.6.13

.NET 8.0 This package targets .NET 8.0. The package is compatible with this framework or higher. 
dotnet add package PhoenixmlDb.XQuery --version 1.6.13
                    


                    

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


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


                    

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


                            Install as a Cake Addin
                        

                    

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


                            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.13 34 9/4/2026
1.6.12 81 9/1/2026
1.6.11 127 8/29/2026
1.6.10 153 8/29/2026
1.6.9 171 8/27/2026
1.6.8 142 8/26/2026
1.6.7 155 8/24/2026
1.6.6 142 8/23/2026
1.6.5 139 8/21/2026
1.6.2 174 8/16/2026
1.6.1 189 7/31/2026
1.6.0 164 7/27/2026
1.5.5 189 7/12/2026
1.5.4 191 7/9/2026
1.5.3 139 7/8/2026
1.5.2 139 7/7/2026
1.5.1 157 6/30/2026
1.5.0 118 6/28/2026
1.4.7 151 6/25/2026
1.4.6 225 6/17/2026
Loading failed

Two fixes, both the same mistake: a spec-defined operation on `xs:QName` delegating to
`QName.ToString()`, which renders the EQName form `Q{uri}local` as soon as an expanded namespace
is attached. That is a good rendering for a debugger and the wrong one for a value.

This release exists to unblock the XSLT engine. There, `$err:code` could not carry its namespace
URI at all — attaching one changed how the value printed — so a caught error code could never
compare equal to `QName('http://www.w3.org/2005/xqt-errors', 'XTTE0570')`, which is how a
stylesheet (and XSpec) asserts on an error code.

### Casting `xs:QName` to `xs:string` gave the EQName form, not the lexical one

`ConcatFunction.XQueryStringValue` had no QName branch, so the value fell through to
`QName.ToString()`. XPath 3.1 §19.2 requires the lexical form — `prefix:local`, or the bare local
name when there is no prefix.

### `fn:deep-equal` compared QNames by their debug rendering

It fell through to `string.Equals(a.ToString(), b.ToString())`. So the same name spelled two ways
— `Q{uri}local` from a QName carrying an expanded namespace, `prefix:local` from one carrying
only a runtime namespace — compared **unequal**. It now compares namespace URI plus local name
and ignores the prefix: the identical rule the `eq` operator has always applied a few hundred
lines away in the same file. `deep-equal` simply never reached it.

That one was masking a defect in the XSLT engine as well. XSpec's `catch_stylesheet` asserts an
error code against `xs:QName('error-code-of-my-template')`; three of those assertions passed only
because a namespace difference is invisible when both sides render as the bare local name.
Comparing by value turned them red, which is how the XSLT-side bug (an `xmlns=` default leaking
into `xs:QName()` casts) was found and fixed.

`PhoenixmlDb.Core`'s `QName.ToString` is deliberately untouched: the two renderings serve
different audiences, and the fix belongs where the spec-defined conversion happens rather than in
a general-purpose `ToString`.

Measured with the companion XSLT changes on XSpec's 284-suite corpus: five suites better, and the
three that an earlier attempt at this regressed (`yes-no-utils`, `xsl-result-document`,
`external_xslt-package_arith_private`) all back to baseline.