Skip to content

schema:update now wants to DROP the migrations table #139

@hopstad

Description

@hopstad

Im having some issues upgrading from 2.x to 3.x.

If I run schema:validate it says its not in sync. Running the schema:update says it wants to remove the migrations table? How to handle this?

Is it so that update and validate should not be used anymore? and rely only on migrations?

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