Re: [I] Error in applying db migration to azure mysql instance [superset]

["rusackas (via GitHub)" <gi...@apache.org>]

rusackas commented on issue #33855:
URL: https://github.com/apache/superset/issues/33855#issuecomment-4353144303

   Closing this out — it's been ~10 months since the last update. It sounds like you found a working workaround (using `Enum.value` in the migration script, or switching to `mysql+mysqldb`), and the underlying issue with `mysql-connector-python` and Enum handling is well-understood.
   
   If you (or anyone) wants to send a PR to make the migration script Enum-safe so this works out-of-the-box on `mysql+mysqlconnector`, that'd be very welcome — please reopen or link a PR back here. Otherwise, reopen if you're still hitting this on a current version.


-- 
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-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org