ydastous commented on issue #34208: URL: https://github.com/apache/superset/issues/34208#issuecomment-3084567627
Hello @dosu is there a list of other drivers i can try with mysql ? Yves On Thu, Jul 17, 2025 at 11:42 AM dosubot[bot] ***@***.***> wrote: > *dosubot[bot]* left a comment (apache/superset#34208) > <https://github.com/apache/superset/issues/34208#issuecomment-3084551213> > > Hi @ydastous <https://github.com/ydastous>! I'm Dosu > <https://go.dosu.dev/dosubot> and I’m helping the superset team. > > This error is due to a compatibility mismatch between Superset's > result-fetching logic and how the mysql-connector-python driver signals > result set availability for DDL/DML statements like INSERT, CREATE, or > UPDATE. Superset expects the driver to properly indicate when a statement > does not return a result set, but mysql-connector-python sometimes does > not, leading to the "No result set to fetch from" error. Other drivers, > like mysqldb, handle this signaling differently, which is why you don't see > the error there. This is a known class of compatibility issues with > mysql-connector-python in Superset, but there is no documented workaround > or configuration to resolve it as of 4.1.2 reference > <https://github.com/apache/superset/issues/33855> reference > <https://github.com/apache/superset/issues/33157>. > > If you require caching_sha2_password and cannot use mysqldb, you may need > to monitor for upstream fixes or consider alternative approaches, as > Superset's MySQL engine spec does not currently have special handling for > this error with mysql-connector-python. > > *To reply, just mention @dosu <https://go.dosu.dev/dosubot>.* > ------------------------------ > > How did I do? Good > <https://app.dosu.dev/response-feedback/5c75e684-e2c9-41c2-aa13-f125ba0940ee?feedback_type=great_response> > | Irrelevant > <https://app.dosu.dev/response-feedback/5c75e684-e2c9-41c2-aa13-f125ba0940ee?feedback_type=irrelevant_answer> > | Incorrect > <https://app.dosu.dev/response-feedback/5c75e684-e2c9-41c2-aa13-f125ba0940ee?feedback_type=incorrect_sources> > | Verbose > <https://app.dosu.dev/response-feedback/5c75e684-e2c9-41c2-aa13-f125ba0940ee?feedback_type=too_verbose> > | Hallucination > <https://app.dosu.dev/response-feedback/5c75e684-e2c9-41c2-aa13-f125ba0940ee?feedback_type=hallucination> > | Report 🐛 > <https://app.dosu.dev/response-feedback/5c75e684-e2c9-41c2-aa13-f125ba0940ee?feedback_type=bug_report> > | Other > <https://app.dosu.dev/response-feedback/5c75e684-e2c9-41c2-aa13-f125ba0940ee?feedback_type=other> > [image: Join Discord] <https://go.dosu.dev/discord-bot> [image: Share > on X] > <https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/34208> > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/superset/issues/34208#issuecomment-3084551213>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ADFBC5ZIABGW7PIPFQIHDID3I677JAVCNFSM6AAAAACBYGX73WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOBUGU2TCMRRGM> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- 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: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
