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 2021/09/30 02:33:07 UTC

[GitHub] [superset] SamEBae commented on issue #16909: [Deploy]superset db upgrade failed 1.2.0 to 1.3.0 upgrade

SamEBae commented on issue #16909:
URL: https://github.com/apache/superset/issues/16909#issuecomment-930700591


   @junlincc 
   might be newb question, but i was thinking of forcing the alembic migration somehow or reset it.
   let me know if there's other reference of that on other issue or if that's even the right approach


-- 
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