[pgvector] Something in the generated tests is trying to drop the vector type, causing them to fail.

[RuurdBijlsma]

Hello, I'm using Loco and have made a bunch of migrations to set up my database, entities, models and tests. In some of these migrations I use the vector type from pgvectors. After some figuring out it works pretty well, I just have to change the type of the generated entity from this

    #[sea_orm(column_type = "custom(\"vector\")")]
    pub embedding: String,

to this

    #[sea_orm(column_type = "custom(\"vector\")", select_as = "float4[]")]
    pub embedding: Vec<f32>,

In the playground I can use this type fine.

However, the generated tests all fail, all with the following error:

---- models::users::can_set_forgot_password_sent stdout ----
thread 'models::users::can_set_forgot_password_sent' panicked at tests\models\users.rs:182:10:
Failed to boot test application: DB(Exec(SqlxError(Database(PgDatabaseError { severity: Error, code: "2BP01", message: "cannot drop type vector because extension vector requires it", detail: None, hint: Some("You can drop extension vector instead."), position: None, where: None, schema: None, table: None, column: None, data_type: None, constraint: None, file: Some("dependency.c"), line: Some(787), routine: Some("findDependentObjects") }))))

This is the line that produces the error:

    let boot = boot_test::<App>()
        .await
        .expect("Failed to boot test application");

First I thought this was because I wasn't dropping the vectors extension correctly in my migrations, so I made it into a separate migration that runs first, but that didn't fix it. This is my first migration:

    async fn up(&self, m: &SchemaManager) -> Result<(), DbErr> {
        let db = m.get_connection();
        db.execute_unprepared("CREATE EXTENSION IF NOT EXISTS vector")
            .await?;
        Ok(())
    }

    async fn down(&self, m: &SchemaManager) -> Result<(), DbErr> {
        let db = m.get_connection();
        // I was hoping the DROP EXTENSION with CASCADE here would resolve the vector type issue.
        db.execute_unprepared("DROP EXTENSION IF EXISTS vector CASCADE")
            .await?;
        Ok(())
    }

Removing the DROP EXTENSION line doesn't change the error. Also all down migrations work correctly, I can run cargo loco db down 17 to revert all migrations without issue.

So now I have no idea how to fix it, and I'm hoping someone with deeper knowledge of what component is trying to drop the vector type can help. I'm new to Rust so I'm still pretty useless in solving this stuff myself.

My full code is here if that helps: https://github.com/RuurdBijlsma/photos-backend/tree/develop

The full output of the failing tests is here: https://github.com/RuurdBijlsma/photos-backend/actions/runs/13484032328/job/37672868935?pr=2#step:6:2052

[RuurdBijlsma]

Found out it does work on the first test on a clean db, with this info I got this workaround:

#[tokio::test]
#[serial]
async fn test_model() {
    configure_insta!();

    let boot = boot_test::<App>().await.unwrap();
    seed::<App>(&boot.app_context).await.unwrap();
    helpers::teardown(&boot.app_context.db).await;
}

with helpers::teardown:

pub async fn teardown(db: &DatabaseConnection) {
    db.execute_unprepared("DROP EXTENSION IF EXISTS vector CASCADE")
        .await
        .expect("Ono!");
}

i have to add helpers::teardown(&boot.app_context.db).await; at the end of every test now, but at least it works.

If anyone has more knowledge about this and has a better way to solve it I'd still love to hear it. I know there's a truncate function in app.rs, but adding the DROP EXTENSION there doesn't work, so that doesn't seem to be called after every test, even though i do have dangerously_truncate on in my test config.