Skip to content

Conversation

@bh2smith
Copy link
Owner

There was an inconsistency with the types returned from postgres and those being passed in.

PG.fetch returned DataFrame
but
PG.save expected TypedDataFrame

Resulted in a bug where data.is_empty did not exist.

This PR aligns the types naively, but this will all be improved in a follow up #129 (which assigns proper/non-empty types) to Postgres dataframes.

Copy link
Collaborator

@mooster531 mooster531 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch!

@bh2smith bh2smith merged commit b130bb7 into main Dec 25, 2024
3 checks passed
@bh2smith bh2smith deleted the pg/is_empty branch December 25, 2024 15:01
bh2smith added a commit that referenced this pull request Dec 26, 2024
This PR started as a coverage improvement. 
However, we found that config did not need to be async and simplified
that flow.
There was also a bug with `make run` (the sample config) introduced in
#130 with the `DataFrame` to `TypedDataFrame` switch.

This resolves all of that while bringing coverage to 96% (also ignoring
main).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants