dbDBKraftDocs
Documentation/DBA modules
Chapter 24

Version History

Object-level revision history, like a document’s version history. Available as the fourth tab of Schema Tools.

#24.1How versions are captured

  • Automatically. Every CREATE OR REPLACE you execute in the SQL editor snapshots that object’s DDL as a new version. You do not have to do anything.
  • Manually. Select an object and press Snapshot to save its current state. If nothing has changed since the newest version, DBKraft says so and does not create a duplicate.
  • Automatically before a restore. Restoring a version first snapshots the current state, so every restore is itself reversible.

#24.2The three panes

Left — Objects. Every object with history, searchable, showing owner, type badge and version count.

Centre — DDL viewer. The selected version’s DDL. When a previous version exists, a Changes vs vn toggle switches between the plain DDL and a line diff: additions in green with +, deletions in red with -, unchanged lines dimmed. Very large sources skip the diff and show the plain DDL.

Above the DDL: Copy (copies the DDL to the clipboard) and Restore this version.

Right — Versions timeline. Newest first, each entry showing the version number, a source badge, and the timestamp:

BadgeOrigin
CompiledCaptured automatically from a CREATE OR REPLACE.
SnapshotYou pressed Snapshot.
RestoredProduced by restoring an earlier version.
Before restoreThe automatic safety snapshot taken immediately before a restore.

Hover a version for two icons: Name this version (attach a label such as "Before Q3 release") and Delete version.

#24.3Restoring

Restore this version asks for confirmation, then recompiles the object from that version’s DDL against the live database. The confirmation dialog reminds you that the current state is snapshotted first.

Restoring runs DDL against your database. On Oracle, DDL commits implicitly — see §16.6.