PhoenixmlDb.XQuery 2.0.0

dotnet add package PhoenixmlDb.XQuery --version 2.0.0
                    
NuGet\Install-Package PhoenixmlDb.XQuery -Version 2.0.0
                    
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.0.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="PhoenixmlDb.XQuery" Version="2.0.0" />
                    
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.0.0
                    
#r "nuget: PhoenixmlDb.XQuery, 2.0.0"
                    
#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.0.0
                    
#: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.0.0
                    
Install as a Cake Addin
#tool nuget:?package=PhoenixmlDb.XQuery&version=2.0.0
                    
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 supportjson-doc(), parse-json(), maps, arrays — query JSON natively
  • Full-text searchcontains 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.0.0 0 9/15/2026
1.8.0 178 9/14/2026
1.7.0 587 9/11/2026
1.6.15 134 9/9/2026
1.6.14 162 9/7/2026
1.6.13 145 9/4/2026
1.6.12 171 9/1/2026
1.6.11 146 8/29/2026
1.6.10 172 8/29/2026
1.6.9 229 8/27/2026
1.6.8 163 8/26/2026
1.6.7 169 8/24/2026
1.6.6 155 8/23/2026
1.6.5 150 8/21/2026
1.6.2 187 8/16/2026
1.6.1 199 7/31/2026
1.6.0 174 7/27/2026
1.5.5 201 7/12/2026
1.5.4 202 7/9/2026
1.5.3 150 7/8/2026
Loading failed

**Major because existing queries stop compiling.** Part of the coordinated
namespace-consolidation train: `PhoenixmlDb.Core`, `PhoenixmlDb.XQuery` and `PhoenixmlDb.Xslt`
all move to 2.0.0 together. Takes **PhoenixmlDb.Core 2.0.0**.

### Breaking — read this before upgrading

**1. The extension functions have moved to `phx`, and the old names no longer compile.**

`ft:*` and `dbxml:metadata` are gone. There are no aliases — this is a clean break, so a query
using the old names fails at compile time rather than behaving differently.

| was | now |
|---|---|
| `dbxml:metadata` | `phx:metadata` |
| `ft:stem` | `phx:stem` |
| `ft:tokenize` | `phx:tokenize` |
| `ft:score` | `phx:score` |
| `ft:is-stop-word` | `phx:is-stop-word` |
| `ft:thesaurus-lookup` | `phx:thesaurus-lookup` |

`phx` is **predeclared** — bound to `https://schemas.phoenixml.dev/2026/functions` — so no prolog
declaration is needed. The old `http://www.w3.org/2007/xpath-full-text` namespace is retired, and
with it the misleading suggestion that these were standard functions. They never were: the W3C
Full Text specification defines the `contains text` clause and no callable functions in that
namespace.

**2. A host can no longer bind `phx` to another URI.** Passing a different `phx` binding through
`CompilationOptions.StaticNamespaces` is now a compile error. If your documents use `phx` as
their own prefix, declare it in the query prolog, exactly as you would for `math:`.

**3. `IMetadataProvider` never receives a prefixed key.** Keys arrive as `local` or
`Q{uri}local`. The system key `dbxml:size` now arrives as
`Q{https://schemas.phoenixml.dev/2026/meta}size`. Custom providers matching on the literal
`dbxml:` prefix must be updated.

### Added

- **Prolog-declared prefixes now work in metadata keys.** A key written `p:local` resolves `p`
 through the query's own `declare namespace`, not only the container's bindings.

### Fixed

- **In-scope namespaces survive copies and serialization.** A copied element kept the namespaces
 it needed to serialize correctly, and `fn:in-scope-namespaces` now comes from the same walk
 rather than a second implementation that could disagree.
- **Serialization parameters are read properly**: every parameter the serializer supports,
 `output:item-separator` from the prolog, and a parameter-document through the same path.
- **An unresolvable namespace id fails loudly when serializing** instead of producing output with
 a wrong or empty namespace.
- **An XML declaration is written for a bare element** when one is requested.

### Conformance

W3C QT3 **29,813**.