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 2020/01/10 00:32:51 UTC
[GitHub] [incubator-superset] thejuan commented on issue #8297: DB migration
937d04c16b64 -> 7f2635b51f5d fails
thejuan commented on issue #8297: DB migration 937d04c16b64 -> 7f2635b51f5d fails
URL: https://github.com/apache/incubator-superset/issues/8297#issuecomment-572819925
I'm having the same issue. It looks like a previous migration adds a null into column_name
```
INFO [alembic.runtime.migration] Running upgrade 18dc26817ad2 -> c617da68de7d, form nullable
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1244, in _execute_context
cursor, statement, parameters, context
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 552, in do_execute
cursor.execute(statement, parameters)
psycopg2.IntegrityError: null value in column "column_name" violates not-null constraint
DETAIL: Failing row contains (2019-11-20 00:48:48.196223, 2019-11-20 00:48:48.196238, 742, 57, null, f, t, null, f, f, null, 7, 7, null, null, null, null).
```
----------------------------------------------------------------
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