hodgesrm commented on issue #13285:
URL: https://github.com/apache/superset/issues/13285#issuecomment-785492534
Hello @suedschwede, I'm testing this case and need some advice on the
problem you are seeing. To check datatypes I made a small table and added a
row to enable queries.
```
CREATE TABLE superset_test (
`basic_string` String,
`nullable_string` Nullable(String),
`lowcard_string` LowCardinality(String),
`basic_datetime` DateTime,
`nullable_datetime` Nullable(DateTime)
) ENGINE = TinyLog;
INSERT INTO superset_test VALUES('basic', 'nullable', 'lowcard', now(),
now());
```
I can see the effect of syncing columns in the Edit Dataset view. The data
types that return are STRING, NULLABLE(STRING), LOWCARDINALITY(STRING),
DATETIME, NULLABLE(DATETIME). It looks as if the SQLAlchemy driver is getting
these out of system.columns. A couple of questions:
1. Is the expected behavior to see just STRING and DATETIME? Or would you
expect SQL types like VARCHAR?
2. Are there cases where these vendor-specific datatypes cause failures?
3. Are there other places where these types appear and cause problems?
It looks as Sqllite returns standard SQL types by comparison.
Thanks! I appended a copy of the Edit Dataset view mentioned above.
Cheers, Robert
----------------------------------------------------------------
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]
