DbSchema reaches Daffodil DB in embedded or network server mode, reverse engineers tables and views into ER diagrams, and adds SQL editing and HTML documentation for this pure-Java relational store.
Trusted by teams at
An embedded Daffodil DB ships inside the application, and its structure ships inside the source code. Auditors, new hires, and integration partners see nothing until someone reads the code out loud.
DbSchema connects in embedded or network mode and gives the database what it never had: a diagram, a query workbench, and documentation anyone can open.
The same desktop workflow whether the database is a server or a file.
Point DbSchema at the network server or the embedded database and get tables, views, and column definitions on a diagram canvas.
Run statements against the connected instance, validate query logic, and investigate data anomalies without a separate CLI.
Design schema edits on the model and inspect the generated DDL before anything reaches a production Daffodil DB instance.
Commit the Daffodil DB model into the same repository as the application that embeds it. Reviewers see structural changes as ordinary diffs, and DbSchema turns the merged result into DDL for the database.
Network server mode uses jdbc:daffodilDB_net://host:3456/dbname, with 3456 as the
default port; embedded mode uses jdbc:daffodilDB_embedded:dbname. The driver comes
from the Daffodil Software website and registers in DbSchema's driver manager — see the
Daffodil DB JDBC driver page. In embedded mode a
single JVM holds an exclusive lock on the database, so stop the host application before
DbSchema connects.
Free to download, no signup — Architect features free for 15 days.
Teams working with Daffodil DB often use these engines too. Explore dedicated guides and JDBC setup for each.