mistercrunch commented on pull request #10955: URL: https://github.com/apache/incubator-superset/pull/10955#issuecomment-703014535
Is this related to the lingering unique constraint on "db_id + table_name"? We've had this issue where at some point we created a unique constraint on those 2 fields, without including "schema" which should probably be in there too, as you may have a table called "users" in two different schemas. Anyhow, not sure on the status, but the database migrations are trying to delete that constraints but fail on some engines since the name of the constraint is not deterministic and alembic has a blind spot in that area. I feel like it's an issue since 2017 and keep coming back. There's some other nonsense around NULL schema VS empty string and all of it is driving me insane. My last attempt to fix this is held up and was trying to [desperately] remove the constraint creation from the original migration that introduced it. https://github.com/apache/incubator-superset/pull/9882 ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
