axiom-audit-database-schema

To audit SQLite schema migrations for structural anti-patterns, you analyze migration scripts to automatically identify dangerous operations like non-idempotent ALTER TABLE statements or destructive DROP commands, preventing critical data loss and crashes.

Migration idempotency ensures that database migration scripts can be run multiple times without causing duplicate structural changes or data corruption. Validating idempotency is crucial to prevent silent integrity failures and ensure robust data persistence during schema evolution.

Yes, you can verify foreign key enforcement in GRDB databases. The audit process checks that foreign key constraints are properly enabled and validated, which actively prevents orphaned data and maintains relational integrity across schema changes.

To check if batch database operations are wrapped in transactions, scan your schema setup to identify batch operations lacking proper transaction wrapping. This audit prevents disk I/O bottlenecks and optimizes overall database performance.

Auditing GRDB schema changes automatically focuses on structural anti-patterns, migration idempotency, and transaction atomicity. It targets development workflows involving schema evolution and migration testing, but does not fix runtime data conflicts outside the audited migration scripts.