dosubot[bot] commented on issue #37578: URL: https://github.com/apache/superset/issues/37578#issuecomment-3824269658
<!-- Answer --> Superset 6.0.0 does not officially support MariaDB as a metadata database. The documentation and codebase only mention PostgreSQL and MySQL as tested and recommended options for the metadata backend, with no reference to MariaDB support or workarounds for issues like the SQLAlchemy sequence syntax error you encountered ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/installation/architecture.mdx#L48-L53)). The root cause of your error is SQLAlchemy generating a `CREATE SEQUENCE ... NO CYCLE` statement, which MariaDB does not support. This was fixed in SQLAlchemy 2.0.46, but upgrading to SQLAlchemy 2.x in Superset 6.0.0 requires additional code changes and is not a drop-in solution. There are no documented workarounds or patches for using MariaDB as the metadata database in Superset 6.0.0. The recommended alternatives are PostgreSQL or MySQL, as these are the only databases officially tested and supported for metadata storage in production ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/installation/architecture.mdx#L48-L53)). <!-- 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/e9e07967-5002-41b3-ac56-3e554bc04bef?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e9e07967-5002-41b3-ac56-3e554bc04bef?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e9e07967-5002-41b3-ac56-3e554bc04bef?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e9e07967-5002-41b3-ac56-3e554bc04bef?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e9e07967-5002-41b3-ac56-3e554bc04bef?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e9e07967-5002-41b3-ac56-3e554bc04bef?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e9e07967-5002-41b3-ac56-3e554bc04bef?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Superset%206.0.0%20does%20not%20officially%20support%20MariaDB%20as%20a%20metadata%20database.%20The%20documentation%20and%20codebase%20only%20mention%20PostgreSQL%20and%20MySQL%20as%20tested%20and%20recommended%20options%20for%20the%20metadata%20backend%2C%20with%20no%20reference%20to%20MariaDB%20support%20or%20workarounds%20for%20issues%20like%20the%20SQLAlchemy%20sequence%20syntax%20error%20you%20encountered%20%28%5Bsource%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/installation/architecture.mdx%23L48-L53%29%29.%0A%0AThe%20root%20cause%20of%20your%20error%20is%20SQLAlchemy%20generating%20a%20%60CREATE%20SEQUENCE%20...%20NO%20CYCLE%60%20statement%2C%20which%20MariaDB%20does%20not%20support.%20 This%20was%20fixed%20in%20SQLAlchemy%202.0.46%2C%20but%20upgrading%20to%20SQLAlchemy%202.x%20in%20Superset%206.0.0%20requires%20additional%20code%20changes%20and%20is%20not%20a%20drop-in%20solution.%0A%0AThere%20are%20no%20documented%20workarounds%20or%20patches%20for%20using%20MariaDB%20as%20the%20metadata%20database%20in%20Superset%206.0.0.%20The%20recommended%20alternatives%20are%20PostgreSQL%20or%20MySQL%2C%20as%20these%20are%20the%20only%20databases%20officially%20tested%20and%20supported%20for%20metadata%20storage%20in%20production%20%28%5Bsource%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/installation/architecture.mdx%23L48-L53%29%29.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=ht tps%3A//github.com/apache/superset/issues/37578) -- 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]
