The superset db upgrade，the script not executed

[worker24h]

Bug description

root@superset-588675d6f7-52vtb:/app#
root@superset-588675d6f7-52vtb:/app# superset db upgrade
2025-01-16 15:57:24,377:DEBUG:superset.utils.logging_configurator:logging was configured successfully
2025-01-16 15:57:24,381:DEBUG:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
/usr/local/lib/python3.10/site-packages/flask_limiter/extension.py:333: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend.
  warnings.warn(
2025-01-16 15:57:24,461:INFO:superset.utils.screenshots:No PIL installation found
2025-01-16 15:57:24,749:INFO:superset.utils.pdf:No PIL installation found
WARNI [alembic.env] SQLite Database support for metadata databases will         be removed in a future version of Superset.
INFO  [alembic.env] Starting the migration scripts.
INFO  [alembic.runtime.migration] Context impl SQLiteImpl.
INFO  [alembic.runtime.migration] Will assume transactional DDL.
INFO  [alembic.env] Migration scripts completed. Duration: 00:00:00
root@superset-588675d6f7-52vtb:/app#

1. I used MYSQL to store metadata，not sqlite
2. The upgrade command executed success， but the table hasn't changed

Screenshots/recordings

No response

Superset version

4.1.1

Python version

3.10

Node version

18 or greater

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

I found a similar unsolved discussion regarding the issue of multiple head revisions during the superset db upgrade command. You can view it here ^[1].

Regarding your issue, it seems like the migration scripts are not being applied to your MySQL database, even though the command executes successfully. Here are a few things you might want to check:

1. Database Connection Configuration: Ensure that your SQLALCHEMY_DATABASE_URI in superset_config.py is correctly pointing to your MySQL database and not to an SQLite database. This configuration is crucial for directing the migrations to the correct database.

2. Alembic Heads: Check if there are multiple heads in your Alembic migrations. You can do this by running alembic heads to see if there are any discrepancies. If there are multiple heads, you might need to resolve them by merging branches or specifying a specific head.

3. Migration Scripts: Verify that the migration scripts are correctly set up to apply changes to your MySQL database. Sometimes, specific migrations might have conditions that only apply to certain database types.

4. Logging: Increase the logging level to DEBUG in your alembic.ini file to get more detailed output, which might help identify where the process is failing.

If these steps do not resolve the issue, you might want to look into any specific migration scripts that could have issues with MySQL, as there was a known issue with migration scripts in Superset 4.1.1 related to MySQL 8.0 ^[2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}