Pages on ForgeSchema.com

About ForgeSchema

Mon, 01 Jan 0001 00:00:00 +0000

ForgeSchema is a schema evolution engine being developed in Go for PostgreSQL. It makes a proposed change understandable before execution and provides a way to check the result independently afterwards.

All six prototype checkpoints are complete. The CLI validates desired schemas, inspects PostgreSQL 16/17, generates explained plans, applies supported reviewed artifacts transactionally and verifies structural matches or drift without changing the database. The reproducible customer walkthrough and final handoff are available.

Contact

Mon, 01 Jan 0001 00:00:00 +0000

For questions about ForgeSchema, write to info@forgeschema.com.

Technical issues and reproducible problems can also be raised through the project repository. Please use synthetic examples when describing schema problems; database credentials and private data are not needed.

Download

Mon, 01 Jan 0001 00:00:00 +0000

ForgeSchema v0.1.0-alpha.1 is the first public alpha prerelease, licensed under Apache 2.0. Download the CLI for your operating system and processor from the GitHub release. This is an early prototype with a deliberately limited migration contract.

Platform	Processor	Archive
Linux	x86-64 / Intel or AMD	Download
Linux	ARM64	Download
macOS	x86-64 / Intel or AMD	Download
macOS	ARM64 / Apple silicon	Download
Windows	x86-64 / Intel or AMD	Download
Windows	ARM64	Download

Download SHA256SUMS alongside your archive. Compare its SHA-256 digest with the matching line before extracting: use sha256sum on Linux, shasum -a 256 on macOS or Get-FileHash -Algorithm SHA256 in PowerShell. Each archive includes the executable, license, notices and command/operation guides.

Engine

Mon, 01 Jan 0001 00:00:00 +0000

ForgeSchema uses one canonical representation for desired YAML, inspected catalogs, migration plans and independent verification. Supported structural changes can be reviewed as explicit operations before they are executed.

Apply validates the saved artifact, checks the live source after acquiring locks, executes supported operations, verifies the target and commits history atomically. The standalone verify command checks a schema file or a saved ready plan’s target in a separate read-only snapshot.

Verification reports deterministic differences for missing or unexpected objects, types, nullability and ordered key/index definitions. It does not infer renames, generate repairs or read application rows. The current version is a development prototype for PostgreSQL 16 and 17, with deliberately limited schema support.

Interactive Demo

Mon, 01 Jan 0001 00:00:00 +0000

Explore a real ForgeSchema migration below. Choose a recorded PostgreSQL version, compare schemas, open the SQL operations and switch between matching and drift reports. This browser demo replays verified CLI results; it does not connect to a database or execute SQL.

Open the full-width demo

The six-session prototype walkthrough passed on PostgreSQL 16.10 and 17.6. Both runs applied six operations, preserved the two original customer rows, rejected stale replay and detected an extra column without repairing it. The downloadable reports belong to those captured runs; generate fresh plans for another database.

Roadmap

Mon, 01 Jan 0001 00:00:00 +0000

The initial six-session prototype is complete: strict schema validation, PostgreSQL inspection, explained migration planning, transactional execution, independent verification and a reproducible customer-database walkthrough.

The full suite and fresh-checkout walkthrough passed on PostgreSQL 16.10 and 17.6. Tests cover preserved rows, stale plans, competing clients, lock-wait drift, cancellation, statement timeouts and rollback after SQL, target-check, metadata-bootstrap or history-recording failures. These results do not establish general crash recovery or production readiness.

The resume checkpoint records the evidence and handoff. Further work awaits owner direction. The engine is licensed under Apache License 2.0. The first alpha release now provides CLI binaries for Linux, macOS and Windows; see downloads.

Schema Format

Mon, 01 Jan 0001 00:00:00 +0000

Desired schemas and inspected snapshots share a versioned representation of one managed PostgreSQL schema. Tables declare supported columns, primary keys and ordinary indexes. Type aliases and nonsemantic ordering normalize; ordered key and index columns remain significant.

Rename intent belongs in a separate explicit mapping file. Reviewed plans contain the canonical source and target descriptions, fingerprints, explained operations and quoted SQL. Their strict JSON loader rejects malformed and inconsistent artifacts.

Verification compares the complete supported managed schema. Extra tables, columns or indexes are drift, rather than being ignored as unrelated. A structure outside the inspector’s supported representation produces an error instead of a partial report. A match concerns structural metadata, not application data or migration history.

Workflow

Mon, 01 Jan 0001 00:00:00 +0000

Inspect captures the supported PostgreSQL catalog structure. Plan compares that snapshot with a desired schema and explicit rename mappings. Unsupported proposals are blocked with no partial operation list. A ready artifact can be saved and reviewed before apply.

Apply executes that saved supported artifact after validation and a source drift check performed after table locks are acquired. Target verification and migration history share the transaction with the application DDL. External DDL must be paused: relation locks cannot prevent every unrelated schema-level CREATE.