mistercrunch commented on issue #31586: URL: https://github.com/apache/superset/issues/31586#issuecomment-2715466333
Not sure how to make it easier to discover/workaround this issue. This will happen anytime you're "ahead of database migration", where `alembic` keeps a list of database version, and gets lost if you switch from a branch with a new migration that doesn't exist in the branch you're in at that moment. Note that it's possible to `superset db downgrade` to the latest shared database migration between the two branches, but that's pretty involved and generally nuking the Postgres is the right fix. That's relevant in cases where you want to maintain the database state for a reason or another. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
