Skip to content

Running same migration twice creates an error #3

@extragornax

Description

@extragornax

Hello,

Is there a way to "keep track" of the last ran migration to not run it again ?
Similar to db:migrate which then pushes to the database some information to keep track of that

This is to prevent the migration from crashing because "field already exists" or other similar issues

Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions