Checking non-null fields on inserts

[Ddystopia]

Is your feature request related to a problem? Please describe.

My attitude toward sqlx was that if it compiles, than db will not throw error at me at runtime.

Of course sqlx cannot check any possible constraint at compile time, but it can at least catch the most common stuff: adding a new non-null column to db.

Example:

use sqlx::PgPool;

fn main() {
    println!("Hello, world!");
}

struct User {
    id: i32,
    name: String,
    #[expect(dead_code)] // obviously that field would be used somewhere else in database and we cannot rely on that warning
    surname: String,
}

#[expect(dead_code)]
async fn insert(pool: PgPool, user: User) {
    // developer forgot to update insert query and compiler did not warn about it
    sqlx::query!(
        "INSERT INTO user (id, name) VALUES ($1, $2)",
        user.id,
        user.name
    )
    .execute(&pool)
    .await
    .unwrap();
}

Migrations:

• initial:

create table user (id serial primary key, name text not null);

• second:

alter table user add column surname varchar(255) not null;

Describe the solution you'd like
I expect sqlx to catch basic cases when non-null constraints are violated.

Describe alternatives you've considered

1. Doing nothing
2. Workarounds with macros with asserts that every field is used in some way