You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi and thanks for sending the extension trough. I was curious and trying this out, but I bumped in this, and though of reporting it:
LOAD sheetreader;
FROM sheetreader('path/to/test.xlsx');
Returns for me:
INTERNAL Error: Failed to bind "sheetreader": Table function must return at least one column
This error signals an assertion failure within DuckDB. This usually occurs due to unexpected conditions or errors in the program's logic.
For more information, see https://duckdb.org/docs/dev/internal_errors
It seems that providing types is all it's needed to solve the problem:
LOAD sheetreader;
FROM sheetreader('path/to/test.xlsx', types=[BOOLEAN,VARCHAR]);
Unsure whether this needs actual solving or just forcing parameter to be provided.
File was generated like:
LOAD spatial;
COPY (SELECT 1337 as i, 'foobar' as f) TO '__TEST_DIR__/test.xlsx' WITH (FORMAT GDAL, DRIVER 'xlsx');
The text was updated successfully, but these errors were encountered:
I will look into this -- I think the issue is, that the normal logic for determining the column types needs at least two rows -- this heuristic is not used, when you provide the types.
I'll add a more graceful handling for these one row cases 👍
Hi and thanks for sending the extension trough. I was curious and trying this out, but I bumped in this, and though of reporting it:
Returns for me:
It seems that providing types is all it's needed to solve the problem:
Unsure whether this needs actual solving or just forcing parameter to be provided.
File was generated like:
The text was updated successfully, but these errors were encountered: