Compile time checking not catching an error after a not null column + foreing key migration

[BalaBoi]

Query bypassing SQLx compile-time checks for missing NOT NULL column

Background

I've recently added a new required column to my database but I'm noticing that my SQLx query is still compiling successfully despite not including this column. Here's what I've done:

1. Added a migration that adds a NOT NULL column to my table:

ALTER TABLE task
ADD COLUMN user_id uuid NOT NULL;

ALTER TABLE task
ADD CONSTRAINT fk_task_users FOREIGN KEY (user_id)
REFERENCES users(user_id);

2. Restarted my database to ensure changes are applied.

3. My query still compiles despite not including the new required column:

#[instrument]
pub async fn create_new_task(pool: &PgPool, title: &str, description: &str) -> Result<()> {
    sqlx::query!(
        r#"
        INSERT INTO task (title, description)
        VALUES ($1, $2)
        "#,
        title,
        description
    )
    .execute(pool)
    .await?;
    Ok(())
}

Expected Behavior

I expected SQLx to produce a compile-time error because my query doesn't include the new user_id column that's marked as NOT NULL in the database schema.

Actual Behavior

The code compiles successfully but fails at runtime with a PostgreSQL error about violating the not-null constraint.

Environment Details

• Database: PostgreSQL
• Rust version: 1.85
• SQLx Dependency: sqlx = { version = "0.8.3", features = ["runtime-tokio-native-tls", "postgres", "macros", "uuid", "time"] }

Questions

1. Why isn't SQLx catching this missing required column at compile time?
2. Is there a configuration I need to enable to ensure these kinds of errors are caught during compilation?
3. Could this indicate an issue with how my database connection is set up for compile-time checking?

Thank you for any insights on how to resolve this! I really value the compile-time checking feature of SQLx and want to make sure I'm using it correctly.