Skip to content

migrations #7

@Parth

Description

@Parth
  • generate a trait for migrating between two versions, where the unknown tables are required impl's from the creator of the migration
  • use a file extension and provide guidance on whether a migration is required
  • fundamentally if multiple clients are sharing a log (after file locks #6) and one does the migration, and you are running older db code and come across an un-recognized log, you should fail to init.

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