Excel Extension fails to load all data even though stop_at_empty = false

Open
#64 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
databases

Research direction

Start by running the provided Python query against the reproduced D:/test.xlsx input and inspect the read_xlsx entry point used by the Excel extension. Compare the result when an empty column separates populated cells with the expected three-column output, then add coverage showing that stop_at_empty=false preserves the later data and run the relevant tests.

Written by the indexing model from the issue text.

Description

reproduced
What happens?

When there is an empty column in the sheet, duckdb stops at that column.

To Reproduce

Code:

import duckdb

print(
    duckdb.sql(
        "SELECT * FROM read_xlsx('D:/test.xlsx', all_varchar=true, header=false, stop_at_empty=false, ignore_errors = true);"
    ).fetchall()
)

Content of D:/test.xlsx:

A B C
1 X
2
3 X

Result:
[('X',), (None,)]

Expected:
[('X', None, None), (None, None, None), (None, None, X)], or at least [('X',), (None,), (None,)]

OS:

Windows x86_64

DuckDB Package Version:

1.3.2

Python Version:

3.13.7

Full Name:

Luna Yao

Affiliation:

Self

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have tested with a stable release

Did you include all relevant data sets for reproducing the issue?

Yes

Did you include all code required to reproduce the issue?
  • Yes, I have
Did you include all relevant configuration to reproduce the issue?
  • Yes, I have
Dominant language
Python
Stars
186
Forks
113
Avg merge
20h 58m
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from duckdb/duckdb-python

All issues in duckdb/duckdb-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.