PhoenixmlDb.XQuery 2.4.0

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


                    

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


                    

                
#r "nuget: PhoenixmlDb.XQuery, 2.4.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.4.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.4.0
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=PhoenixmlDb.XQuery&version=2.4.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 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.

Takes **PhoenixmlDb.Core 2.0.0** (unchanged).

### Fixed: typed results the conformance harness used to hide (#83, #85)

Before #49 the QT3 harness counted any `assert-type` it didn't recognise as a pass. Once it
checked for real, six engine defects showed up that had passed by default:

| | was | now |
|---|---|---|
| `fn:namespace-uri` | `xs:string` | `xs:anyURI` |
| `fn:prefix-from-QName` | `xs:string` | `xs:NCName` |
| `fn:default-language` | `xs:string` | `xs:language` |
| `map:put` with an equal key of another type | kept the old key | replaces key and value, same position |
| `xs:short(256) cast as xs:numeric` | lost `xs:short` | keeps it |
| `schema-element(unbound:x)` | `XPST0008` | `XPST0081` |

The new types reach code that had only seen plain strings, so these were fixed at the root: one
rule for `xs:string` arguments means `string-to-codepoints`, `codepoint-equal` and
`encode-for-uri` accept `xs:anyURI` and string subtypes, and string constructors accept a
string-subtype source.

### Behaviour changes — read before upgrading

- **`fn:namespace-uri` returns `xs:anyURI`.** Code that tests its result `instance of xs:string`
 gets a different answer.
- **`fn:distinct-values` treats an `xs:anyURI` and an equal `xs:string` as one value**, matching
 this engine's own `eq` and XPath 4.0. This reverses an earlier choice whose spec citation
 didn't hold up.
- **Default output renders `xs:anyURI`, `xs:untypedAtomic` and string subtypes bare**, the same
 way a plain `xs:string` already rendered. Without this, every `namespace-uri()` result
 printed through the facade would have gained quotes. A query that declares
 `output:method "adaptive"` still gets the quoted W3C form.

### Conformance

**W3C QT3: 29,895 / 31,379 (95.27%)**, measured on the release commit. The denominator is
unchanged. #85's per-case diff shows 14 cases newly passing and none newly failing: that fully
recovers the nine the harness correction exposed, plus five more.

The ratchet in `scripts/conformance-baseline.tsv` is raised to this measurement. It hadn't been
raised since before 2.2.0, so part of the raise (+91 across 19 sets) is earlier work that was
never recorded, for example 2.2.0's `xs:IDREFS` cast targets. It is not all this release.

### Upgrading

`PhoenixmlDb.Xslt` 2.4.0 needs its own fix for this change (xslt#188, promoting `xs:anyURI` to
`xs:string` for stylesheet-function parameters). Without it, a stylesheet function receiving
`namespace-uri()` fails. Take the two packages together; the lockstep pins enforce that.

**2.3.0 carried no library change** (it was byte-identical to 2.2.0, a lockstep bump that was
published and then superseded). Moving from 2.2.0 or earlier straight to 2.4.0 is the intended
path.