RadarModel Adds RadarModel Schema for Database Drift

RadarModel shipped its second product the same day as its first. Version 0.2 adds radarmodel-schema, which reads the live schema of a Postgres, MySQL, MariaDB or SQLite database, keeps it, and reports what changed on the next scan: a column dropped by hand, a type changed on production only, an index lost in a rebuild. It needs no migration tool. The first scan is the baseline. The release post has the details, and the 0.2.0 release holds both commands in one archive per system.

A dropped table or column, a changed type or a new NOT NULL is breaking; a dropped index or a changed default is a warning. Baselines can roll, so each change is reported once, or stay pinned until someone runs accept. diff compares two databases right now, staging against production. It only reads: Postgres and MySQL inside read-only transactions, SQLite opened read-only.

The promise is the one from RadarModel AI: never cry wolf. The test write-up runs against real servers, Postgres 12 to 17, MySQL 8.0 and 8.4 and MariaDB 10.6 and 11.4, and makes 16 kinds of manual change for real. Lost connections, revoked privileges, other session settings and a migration running mid-scan are failed scans or no change at all, never drift, and an independent review before release added several of those cases. A schema of 2,000 tables scans in 0.41 seconds on Postgres.