pkg.soopen package index

brew / rank 13069

Install dbxml with Homebrew, Nix

Embeddable XML database with XQuery support and other advanced features. Version 6.1.4 via Homebrew; verified 2026-07-10. Also installable with nix: nix profile install nixpkgs#dbxml.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install dbxml

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#dbxml

nixpkgs package indexes · pkgs/by-name/db/dbxml/package.nix · source: api.github.com

overview

Package summary

Embeddable XML database with XQuery support and other advanced features

Commands and aliases

  • dbxml
  • dbxml_dump
  • dbxml_load
  • dbxml_load_container

history

Project history and usage

Berkeley DB XML is Oracle's embeddable XML database product for applications that wanted native XML storage, indexing, and XQuery without running a separate database server. In package terms it sits at the intersection of Berkeley DB, XML databases, and local command-line database tooling.

Project history

The project grew out of the Berkeley DB family after native XML databases became a practical answer to document-centric data. Oracle's Programmer's Reference Guide describes Berkeley DB XML as a C++ library built around Berkeley DB storage and XML/XQuery components, with documentation for Unix, Windows, language APIs, upgrades, and the dbxml command-line shell.

Its long manual history is visible in Oracle's upgrade and changelog sections, which cover the 1.2 line, the 2.0 through 2.5 series, and 6.0.x releases. The product's technical story is not only file storage: it was about storing XML documents in containers, indexing nodes and metadata, and running XQuery directly against those containers.

Adoption history

Berkeley DB XML belongs to the embedded-database tradition rather than the client/server database tradition. Oracle's FAQ lists C++, Java, Perl, PHP, Python, and Tcl interfaces, so adoption was mostly through applications that linked the library or scripted it locally, not through users connecting to a network daemon.

The product is also a period marker for the 2000s XML-database wave. It appealed to applications with non-tabular, frequently changing, document-shaped data, where an XML repository reduced the mismatch between the application model and relational tables.

How it is used

Typical use is to create Berkeley DB XML containers, insert XML documents, define indexes, and query them with XQuery or XPath-style expressions. The Homebrew package exposes the dbxml shell and dump/load utilities, which makes it useful for local inspection, export/import, and small reproducible database experiments.

The FAQ emphasizes operational concerns familiar to embedded-database users: large documents, node storage containers, explicit resource cleanup in Java bindings, thread-sharing rules for manager/container/query objects, and careful configuration of validation and external access.

Why package nerds care

dbxml is a preserved slice of database packaging history: an embeddable XML database installed as libraries plus command-line utilities. It is interesting precisely because it is neither a modern document service nor a plain key-value store; it packages a whole native-XML data-management worldview into a local Unix toolchain.

Timeline

  • 1.2 era: Oracle's guide records Berkeley DB XML 1.2.0 and 1.2.1 changelog sections.
  • 2.x era: Upgrade notes cover 2.0, 2.1, 2.2, 2.3, 2.4, and 2.5 transitions.
  • 2015: Oracle's Berkeley DB XML Programmer's Reference Guide for library version 12.1.6.0 is dated July 10, 2015.
  • 6.0 era: Oracle's documentation includes 6.0.17 and 6.0.18 changelog sections.

Related projects

  • Berkeley DB XML is closely tied to Berkeley DB, XQilla, Xerces-C, and the language bindings documented by Oracle for C++, Java, Perl, PHP, Python, and Tcl.

security posture

Risk level: orange

broad file, network, media, or database tool signal. infrastructure mutation or orchestration signal.

Risk classifier

orange risk · medium confidence · infrastructure

Why

  • broad file, network, media, or database tool signal
  • infrastructure mutation or orchestration signal

Signals

  • text:container
  • text:database

Install behavior

  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
dbxmlexecutableindexed executableDiscovered from the local executable index.
dbxml_dumpexecutableindexed executableDiscovered from the local executable index.
dbxml_loadexecutableindexed executableDiscovered from the local executable index.
dbxml_load_containerexecutableindexed executableDiscovered from the local executable index.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-08-03
manager version6.1.4
manager updated2026-07-10
local dataunknown
upstreamnot available
latest detectednot detected
  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:dbxml
Version6.1.4
Package managerHomebrew
Homepagehttps://www.oracle.com/database/technologies/related/berkeleydb.html
Last updated2026-07-10T19:03:06-04:00
Pulseupdated
Bottlenot recorded
Servicenone declared

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

dbxml

nix profile install nixpkgs#dbxml
  • normalized package name match
  • Matched by: Dbxml
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/db/dbxml/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation