Migrations involving alter table

[kikijiki]

Assuming I have an enum like this in the first migration file:

#[derive(DeriveIden)]
pub enum Tag {
    Table,
    Id,
    Name,
}

I then create the table like this:

manager
    .create_table(
        Table::create()
            .table(Tag::Table)
            .if_not_exists()
            .col(
                ColumnDef::new(Tag::Id)
                    .integer()
                    .not_null()
                    .auto_increment()
                    .primary_key(),
            )
            .col(ColumnDef::new(Tag::Name).string().not_null())
            .to_owned(),
    )
    .await?;

Now, in a future migration I want to add a new column, Description.
The manager can alter the table just fine, but the existing enum will be out of date.

From the documentation I did not understand how I am supposed to handle this 🤔
Am I supposed to edit the original declaration and add the field there?

In my mind each migration file was meant to be static, representing the DB in that point in time.
Also in case of dropping a column it would make the build fail too.

[tyt2y3]

It depends on where you put the enum Tag? Usually we put the enums in the same file as the migration, so that each migration file is self-contained.

[tyt2y3]

Look at this example? https://github.com/SeaQL/sea-orm/blob/master/examples/seaography_example/migration/src/m20230101_000001_create_bakery_table.rs

In which I also embedded a copy of generated entities for seeding data.

[kikijiki]

Ah I see, makes sense!

So in each new migration file I would just declare a new version of the same enum with the correct fields if needed basically.

Thank you 👍