fix(cursor, fetch_dataframe): use column names in cursor's description as is #239
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.
Previously, the
Cursor.fetch_dataframe
method lowercased column names preemptively, thus not respecting the case-sensitivity configuration value. This could lead to issues, when e.g. two different columns resolved to the same name when lowercased.This PR fixes the issue by ensuring the resulting
DataFrame
's columns are the same as the ones in the cursor'sdescription
attribute, thus making the driver match Redshift's behavior.Motivation and Context
Fixes #238
Testing
Implemented a unit test that demonstrates how
fetch_dataframe
preserves the column names as they appear in the cursor'sdescription
attribute.After making the change, I ran
python -m pytest test/unit
in a fresh environment and observed all tests succeeding:Types of changes
Checklist
./build.sh
succeedspytest test/unit
and they are passing.License