You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2019/12/17 20:59:38 UTC
[GitHub] [incubator-superset] willbarrett commented on issue #8737:
Migration and model changes to synchronize the data model
willbarrett commented on issue #8737: Migration and model changes to synchronize the data model
URL: https://github.com/apache/incubator-superset/pull/8737#issuecomment-566746517
@john-bodley and @mistercrunch - I've looked closely at the constraint in question, and I can find where it is added to the database (https://github.com/apache/incubator-superset/blob/master/superset/migrations/versions/b4456560d4f3_change_table_unique_constraint.py) but cannot find any migration that removes that constraint. It's possible that it was never applied to your MySQL database, but that constraint does exist in postgres. We have two options here:
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org