sqlc generate / vet does not detect outdated INSERT queries after adding a new NOT NULL column

[EliottMartinAive]

Hello !

I would like to describe a case where a schema change can leave older INSERT queries outdated, without sqlc generate or sqlc vet flagging the issue.

Initial migration:

create table if not exists public.babar (
    id uuid not null,
    name text not null,
    created_at timestamp with time zone not null,
    updated_at timestamp with time zone not null,

    constraint babar_pkey primary key (id)
);

Developer 1 creates the table and writes this query:

-- name: CreateBabar :exec
INSERT INTO babar (id, name, created_at, updated_at)
VALUES ($1, $2, $3, $4);

Later, another developer adds a new required column:

alter table babar
    add column description text not null;

That developer also adds a new query that includes the new column:

-- name: CreateBabar2 :exec
INSERT INTO babar (id, name, description, created_at, updated_at)
VALUES ($1, $2, $3, $4, $5);

However, they forget to update the original query CreateBabar, which is still used by another service.

So now the old query is effectively invalid at runtime, because it does not provide a value for description, but:

sqlc generate does not flag it

sqlc vet with sqlc/db-prepare does not flag it either

The problem only appears at execution time.

What I would like is a way for sqlc to detect this kind of issue earlier, ideally during generation, vetting, or some schema/query consistency check.

In other words, for INSERT statements, it would be very useful if sqlc could detect when:

a table has a NOT NULL column with no default value

and an existing query no longer inserts that column

This is especially important in multi-service environments, where one service updates migrations and adds new queries, but older queries may still exist in other files or services and become stale.

Is this something that sqlc could support directly, or is there already a recommended workflow to catch this kind of schema drift before runtime?