Migrator executing same query multiple times for seaql_migrations

[detoxifiedplant]

i have a very similar setup like actix_example
the difference is i don't have any migration file at all, and the only time i'm calling the Migrator is when the application gets initialized with

Migrator::up(&connection, None).await?;

why the same query for seaql_migrations is being executed multiple times as below logs

DEBUG sea_orm::database::transaction: CREATE TABLE IF NOT EXISTS "seaql_migrations" ( "version" varchar NOT NULL PRIMARY KEY, "applied_at" bigint NOT NULL )

INFO sqlx::postgres::notice: relation "seaql_migrations" already exists, skipping

INFO sea_orm_migration::migrator: Applying all pending migrations

DEBUG sea_orm::database::transaction: CREATE TABLE IF NOT EXISTS "seaql_migrations" ( "version" varchar NOT NULL PRIMARY KEY, "applied_at" bigint NOT NULL )

INFO sqlx::postgres::notice: relation "seaql_migrations" already exists, skipping

DEBUG sea_orm::database::transaction: CREATE TABLE IF NOT EXISTS "seaql_migrations" ( "version" varchar NOT NULL PRIMARY KEY, "applied_at" bigint NOT NULL )

INFO sqlx::postgres::notice: relation "seaql_migrations" already exists, 
    
DEBUG sea_orm::database::transaction: CREATE TABLE IF NOT EXISTS "seaql_migrations" ( "version" varchar NOT NULL PRIMARY KEY, "applied_at" bigint NOT NULL )

INFO sqlx::postgres::notice: relation "seaql_migrations" already exists, skipping

DEBUG sea_orm::database::transaction: SELECT "version", "applied_at" FROM "seaql_migrations" ORDER BY "version" ASC

is it due to internal designe or anything wrong with the migration setup? as the actix_example also does the same.

[tomellm]

Since I had the same question and for anyone coming to this in the future: Looking into the source code it seems this is normal and part of the design. Whatever method you call, (in my case get_pending_migrations and up) the Migrator makes sure that it is installed by doing Self::install(db).await?; which causes the selects. So to conclude, while its not the prettiest, its normal and not a problem.

But please do consider that I'm no professional with the sea_orm codebase so im not 100% sure myself. Also I didn't mean any disrespect with this, the product is wonderful! ;)