db-defaults-generated

You audit database schema for correct column defaults and generated columns by running a validation script that checks timestamp defaults, derived value constraints, and sequence ownership. This ensures your relational database maintains data integrity and query performance.

Generated columns should use GENERATED ALWAYS AS STORED to prevent data drift between derived values and their source columns. Storing derived values directly in the database schema ensures non-deterministic defaults remain consistent and maintain strict data integrity.

The difference between serial and GENERATED AS IDENTITY for database sequences involves sequence ownership and syntax hygiene. Auditing identity and sequence configuration validates proper ownership constraints, ensuring reliable auto-incrementing behavior and optimal database performance.

You check if timestamp defaults are set by application code instead of the database by auditing the schema for missing created_at and updated_at default constraints. Correct database-level default configuration prevents inconsistent timestamp generation and improves data integrity.

This schema audit applies to relational databases supporting defaults and generated columns. It requires direct access to the database schema for analysis to validate non-deterministic defaults, NOT NULL constraints, and derived value configurations.

You should not use generated columns for derived values when your relational database lacks support for GENERATED ALWAYS AS STORED syntax. Auditing helps identify missing NOT NULL constraints and dynamic defaults that require alternative application-level configuration approaches.