Data access
Downloads
Download the complete database or choose a focused table export. Provider files are checked against the provider’s pinned checksums at build time; files DemoDB generates (complete JSON, YAML, PostgreSQL script, inGitDB archive, and the MySQL, SQL Server and Oracle scripts written by DataTug and loaded into the real engine) are pinned by a lock and validated against the SQLite fixture; the licence notice below names the ones generated for this dataset.
Every file here, including the JSON and YAML that DemoDB generates from the pinned fixture, contains Shipping data from https://github.com/datatug/datatug-demo-project and is licensed CC0-1.0. Keep the licence and attribution notices with any copy. Source and licence →
Complete database
Files ready to use.
Not offered
Formats without a download.
- PostgreSQL scriptNot available: The pinned Shipping provider has no verified PostgreSQL script for this SQLite schema.
- inGitDB archiveNot available: This SQLite provider does not publish a native inGitDB edition.
- MySQL scriptNot available: No verified MySQL script has been generated for this provider.
- SQL Server scriptNot available: No verified SQL Server script has been generated for this provider.
- Oracle scriptNot available: No verified Oracle script has been generated for this provider.
Machine-readable schema
Use the contract too.
Schema JSON describes native table and view names, columns, keys, relationships, sample rows, and row counts.
Download schema JSON →Reproducible research
One checked snapshot.
The deterministic bundle contains the checked table exports, schema, provider model files, licences, source revision, and example queries. Its manifest lists a SHA-256 checksum for every bundled file and archive part.
Download every part, then concatenate them in numbered order to recreate the ZIP. The manifest lists each part checksum and the complete archive checksum.
Optional browser copy
Explore locally in this browser.
Import every physical table into this browser’s IndexedDB. Nothing is downloaded until you start. Views and the source files stay unchanged; the import is read-only.
The importer verifies the decoded export checksum and declared row count before it activates the new local copy. It uses native primary keys when present; keyless rows are kept in provider JSON export order for local traversal.
No local copy is active.