gtiandClaude Opus 5.5 6bcfac6497 fix: enforce NOT NULL on 20 server-defaulted timestamp columns
Audit of models vs fresh DB vs production (all at 0019): 20 columns are
NOT NULL in the models but nullable in the database, all timestamps with
DEFAULT now() created by 0011/0012/0014/0017 without nullable=False.

Classified DB_CONSTRAINT_MISSING: no application path writes NULL to
them (inserts omit them, updates set now; no raw SQL inserts), and there
were zero NULLs in production and in the development database (246,682
rows checked). The upgrade aborts without changing anything if any NULL
is present, instead of inventing a value.

After this revision a fresh database matches the models on nullability,
column types, PKs, FKs, uniqueness and checks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-23 07:20:04 -03:00
2026-09-21 15:51:47 -03:00
2026-09-21 15:51:47 -03:00
2026-09-21 15:51:47 -03:00
S
Description
GTI GERENCIADOR / FISCAL
11 MiB
Languages
Python 82%
HTML 15.8%
CSS 1.2%
PowerShell 0.6%
Shell 0.2%
Other 0.1%