Closed colpari closed 1 year ago
cc: @betodealmeida
Taking a look, thanks for the detailed info!
In the meantime, a small comment: you don't have to use the meta database name (though you can). So instead of this:
SELECT * from "meta.3cxCallLog%2Ecall_log";
It's better to write:
SELECT * from "3cxCallLog.call_log";
This is definitely a bug coming from the SQLite library, surfaced by apsw. I suspect it's the interval
column. I'll create a similar table in Postgres and test.
OK, I was able to create a similar table (ChatGPT can be awesome) and repro the bug. Working on a fix.
Works in latest-dev - thank you folks!
How to reproduce the bug
SELECT * from "meta.3cxCallLog%2Ecall_log";
)Expected results
Data is returned.
Actual results
Screenshots
Environment
(please complete the following information):
browser type and version: Chromium Version 118.0.5993.70 (Official Build) snap (64-bit)
superset version: The Superset UI shows 0.0.0-dev. We're using this version of the 'latest' image from docker hub with the additional layers
added by us
python version: as in the docker hub image
node.js version: as in the docker hub image
any feature flags active:
FEATURE_FLAGS = {"ALERT_REPORTS": True, "ENABLE_SUPERSET_META_DB": True}
database 3cxCallLog is on a Postgres16 Server but it's maybe worthwhile noting that it was imported from a PG13 Server with
pg_dump -F c | pg_restore -xO
while keeping the original database nameAdditional context
SELECT * from "call_log";
it works as expectedpsql
clientschema of the failing table (holds ~410K records)
schema of the working table in the same database
schema of a more complex table (odoo users table) from another DB (also imported from the same PG13 to the same PG16 with the same command) which works too: