Handle pandas str dtype in COPY#27
Merged
Merged
Conversation
This file contains hidden or 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
1 participant
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.
Summary
Handle pandas 3
strdtype columns in the native pandas COPY scan path.Closes LadybugDB/ladybug#566.
Root cause
Pandas 3 can infer ordinary text columns as
str, represented asStringDtype(storage='python', na_value=nan). The native numpy dtype converter acceptedobjectandstring, but notstr, so dataframe scans reachedUNREACHABLE_CODEbefore COPY could bind the dataframe columns.Changes
strdtype the same as existingobjectandstringtext columns.COPY T FROM dfwith string columns, an integer column, and a nullable double column.