-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DB Upgrade - Fails with sqlalchemy_utils errors #5005
Comments
mistercrunch
added a commit
to mistercrunch/superset
that referenced
this issue
May 15, 2018
3 tasks
mistercrunch
added a commit
that referenced
this issue
May 16, 2018
mistercrunch
added a commit
that referenced
this issue
May 16, 2018
Should be fixed in |
michellethomas
pushed a commit
to michellethomas/panoramix
that referenced
this issue
May 24, 2018
timifasubaa
pushed a commit
to timifasubaa/incubator-superset
that referenced
this issue
May 31, 2018
timifasubaa
pushed a commit
to airbnb/superset-fork
that referenced
this issue
Jul 25, 2018
wenchma
pushed a commit
to wenchma/incubator-superset
that referenced
this issue
Nov 16, 2018
cccs-rc
pushed a commit
to CybercentreCanada/superset
that referenced
this issue
Mar 6, 2024
fixes apache#5005 (cherry picked from commit ea81cb4)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
0.25.2
Expected results
DB upgrade should happen seamlessly.
Actual results
DB upgrade fails on fresh installs.
Steps to reproduce
I was following steps at https://superset.incubator.apache.org/installation.html# and found that the "superset db upgrade" step fails.
On checking, it looks like a wrong import - If I change the
from sqlalchemy_utils.types.encrypted import EncryptedType
tofrom sqlalchemy_utils.types.encrypted.encrypted_type import EncryptedType
it works.The text was updated successfully, but these errors were encountered: