ODB
Generated by scripts/gen-format-pages.py from docs/data/format-metadata/, FILE_FORMATS.csv and docs/formats-master.csv. Do not edit by hand: change the source, then run the script.
OpenDocument Database Preview.
At a glance
| Original creator | OASIS |
| Purpose | The OpenDocument database front end: how to reach a database and which tables, queries, forms and reports are set up on it, with an embedded database if there is one. |
| Extensions | .odb |
| Poka parser | poka-odb |
| Viewer | poka-metadata-card-viewer |
| Depth tier | Metadata card (see Depth tiers) |
| Breadth tier | B3 Core (see Breadth tiers) |
How much Poka reads
B3 Core. Only the main content type or types are decoded (for example geometry but not materials, layers or annotations, or only one version family). The list of gaps is substantial.
Confidence: high (the reviewer read the code and a test that proves the claim). Basis: Reviewed 2026-10-16: parsers/poka-odb/src/lib.rs (content.xml data source, login, filters, tables, queries with SQL, form and report names; forms/, reports/, Basic/ and database/script entries from the package), unit tests, and tests/samples.rs over the 2 corpus .odb (biblio.odb: ODF 1.0 dBASE; LibreOfficeBase_odb_1.3.odb: ODF 1.3 embedded HSQLDB). Covers both connection-resource spellings. Output is a metadata card of the front end, not of the data.
What Poka does not read
- Embedded Firebird databases (driver is named, schema and data are not read; no corpus sample)
- Table data rows (neither HSQLDB script INSERTs as data nor the .data file)
- Parsed schema (columns, types, keys, relations): the HSQLDB script is shown as raw statements, first 120 only
- Tables of an ODF 1.2+ external data source (table representations are not read; names come only from the embedded script)
- Contents of forms and reports (only their names or sub-document entries are listed)
- Query design details beyond name and SQL
- Basic macro source (only library names)
- Password-protected or encrypted packages
Background
An .odb holds no document content: its body is office:database. The Library of Congress describes it as a front end to a local or remote database, stored as a file or reached through a server. Poka shows the connection resource and driver, login settings and table filter, the tables and queries (with each query's SQL), the forms and reports, and for an embedded HSQLDB database the first 120 lines of its SQL script, with the table names taken from it. Both spellings of the connection resource are read: the ODF 1.0 attribute and the ODF 1.2 child element.
Versions
| Version | Identifier | Poka | Note |
|---|---|---|---|
| ODF 1.0 spelling | db:connection-resource attribute |
Read | |
| ODF 1.2 and later spelling | db:connection-resource child element with xlink:href |
Read |
Libraries
Libraries Poka uses or has assessed for this format, with the status, licence and language the registry records.
- quick-xml (used; MIT; Rust)
- zip (used; MIT; Rust)
Software that uses it
- Dassault Systèmes Abaqus
Sources
- https://www.loc.gov/preservation/digital/formats/fdd/fdd000441.shtml
- parsers/poka-odb/src/lib.rs