Skip to content

If there is an exception when applying a migration, there will be an incomplete document at MigrationVersions collection #1

@TioLuiso

Description

@TioLuiso

That leaves the database in an inconsistent status.

I can think of different solutions:

  • Delay the insertion of the MigrationVersion until the migration has been applied
  • In case of an exception, insert in MigrationVersion the exception information, too
  • In case of an exception, remove the entry in MigrationVersion

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions