GitHub user dosubot[bot] added a comment to the discussion: Superset db upgrade is not triggering upgrade
<!-- Answer --> Your log shows that the migration step (`f3c2d8ec8595 -> 9c2a5681ddfd`) is being triggered, which means the upgrade command is running migrations as expected. If you’re not seeing changes in your database or the upgrade isn’t reflected, the most common causes are: - The SQLALCHEMY_DATABASE_URI in your superset_config.py might be pointing to a different database than you expect (for example, SQLite instead of Postgres/MySQL), so migrations are running but not on the intended database. - The alembic_version table in your metadata database might be missing, empty, or have the wrong value, which can cause Alembic to skip or misapply migrations. - There could be a migration failure or database-specific issue (like a deadlock, missing driver, or concurrent access) that isn’t shown in the snippet you posted. To troubleshoot: 1. Check the alembic_version table in your metadata database to confirm the current revision matches the latest migration. 2. Verify that the expected schema changes are present in your database. 3. Double-check that SQLALCHEMY_DATABASE_URI is set to the correct database. 4. If everything looks correct but the schema isn’t updating, try increasing the logging level to DEBUG and look for errors after the migration step. If you can clarify what you expect to see (e.g., a new column, table, or schema change) and what’s actually happening, I can help you narrow it down further. For more details and similar troubleshooting steps, see [this discussion](https://github.com/apache/superset/discussions/33510#discussioncomment-13191574) and [this issue](https://github.com/apache/superset/issues/32846). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/c0d62f9a-1b18-46f8-9bdc-bc9c5db8d86f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/c0d62f9a-1b18-46f8-9bdc-bc9c5db8d86f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/c0d62f9a-1b18-46f8-9bdc-bc9c5db8d86f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/c0d62f9a-1b18-46f8-9bdc-bc9c5db8d86f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c0d62f9a-1b18-46f8-9bdc-bc9c5db8d86f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/c0d62f9a-1b18-46f8-9bdc-bc9c5db8d86f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c0d62f9a-1b18-46f8-9bdc-bc9c5db8d86f?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Your%20log%20shows%20that%20the%20migration%20step%20%28%60f3c2d8ec8595%20-%3E%209c2a5681ddfd%60%29%20is%20being%20triggered%2C%20which%20means%20the%20upgrade%20command%20is%20running%20migrations%20as%20expected.%20If%20you%E2%80%99re%20not%20seeing%20changes%20in%20your%20database%20or%20the%20upgrade%20isn%E2%80%99t%20reflected%2C%20the%20most%20common%20causes%20are%3A%0A%0A-%20The%20SQLALCHEMY_DATABASE_URI%20in%20your%20superset_config.py%20might%20be%20pointing%20to%20a%20different%20database%20than%20you%20expect%20%28for%20example%2C%20SQLite%20instead%20of%20Postgres/MySQL%29%2C%20so%20migrations%20are%20running%20but%20not%20on%20the%20intended%20database.%0A-%20The%20alembic_version%20table%20in%20your%20metadata%20database%20might%20be%20 missing%2C%20empty%2C%20or%20have%20the%20wrong%20value%2C%20which%20can%20cause%20Alembic%20to%20skip%20or%20misapply%20migrations.%0A-%20There%20could%20be%20a%20migration%20failure%20or%20database-specific%20issue%20%28like%20a%20deadlock%2C%20missing%20driver%2C%20or%20concurrent%20access%29%20that%20isn%E2%80%99t%20shown%20in%20the%20snippet%20you%20posted.%0A%0ATo%20troubleshoot%3A%0A1.%20Check%20the%20alembic_version%20table%20in%20your%20metadata%20database%20to%20confirm%20the%20current%20revision%20matches%20the%20latest%20migration.%0A2.%20Verify%20that%20the%20expected%20schema%20changes%20are%20present%20in%20your%20database.%0A3.%20Double-check%20that%20SQLALCHEMY_DATABASE_URI%20is%20set%20to%20the%20correct%20database.%0A4.%20If%20everything%20looks%20correct%20but%20the%20schema%20isn%E2%80%99t%20updating%2C%20try%20increasing%20the%20logging%20level%20to%20DEBUG%20and%20look%20for%20errors%20after%20the%20migration%20step.%0A%0AIf%20you%20can%20clarify%20what%20you% 20expect%20to%20see%20%28e.g.%2C%20a%20new%20column%2C%20table%2C%20or%20schema%20change%29%20and%20what%E2%80%99s%20actually%20happening%2C%20I%20can%20help%20you%20narrow%20it%20down%20further.%20%0A%0AFor%20more%20details%20and%20similar%20troubleshooting%20steps%2C%20see%20%5Bthis%20discussion%5D%28https%3A//github.com/apache/superset/discussions/33510%23discussioncomment-13191574%29%20and%20%5Bthis%20issue%5D%28https%3A//github.com/apache/superset/issues/32846%29.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/37261) GitHub link: https://github.com/apache/superset/discussions/37261#discussioncomment-15544793 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
