Add support for reading/writing .xlsx files
#3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for reading and writing
.xlsxfiles throughCOPY TO/FROM ... FORMAT (XLSX), a newread_xlsx()table function as well as a.xlsxfile replacement scan.The XLSX file parsing is implemented on top of the expat SAX-style xml parsing library and the minizip-ng zip decompression library, enabling large
.xlsxfiles to be read in a streaming fashion over any duckdb supported filesystem with relatively low and constant memory overhead.Im going to update the docs later, but for now you can have a look at the updated
READMEto see how to use this functionality.I've also moved around some stuff in the repository to make it more consistent with the new extension template layout, hence the large diff.