Skip to content

Support pandas.to_sql (fix #101)#110

Merged
laughingman7743 merged 6 commits intomasterfrom
pnadas_to_sql
Jan 13, 2020
Merged

Support pandas.to_sql (fix #101)#110
laughingman7743 merged 6 commits intomasterfrom
pnadas_to_sql

Conversation

@laughingman7743
Copy link
Member

No description provided.

@laughingman7743 laughingman7743 force-pushed the pnadas_to_sql branch 9 times, most recently from 65a251b to 3680ba6 Compare January 5, 2020 13:34
@codecov
Copy link

codecov bot commented Jan 5, 2020

Codecov Report

Merging #110 into master will decrease coverage by 0.09%.
The diff coverage is 93.44%.

Impacted file tree graph

@@           Coverage Diff            @@
##           master    #110     +/-   ##
========================================
- Coverage   92.39%   92.3%   -0.1%     
========================================
  Files          14      14             
  Lines        1104    1156     +52     
========================================
+ Hits         1020    1067     +47     
- Misses         84      89      +5
Impacted Files Coverage Δ
pyathena/pandas_cursor.py 100% <100%> (ø) ⬆️
pyathena/result_set.py 92.25% <100%> (-0.34%) ⬇️
pyathena/cursor.py 100% <100%> (ø) ⬆️
pyathena/sqlalchemy_athena.py 92.85% <92.3%> (-0.54%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9b19bfe...596e32a. Read the comment docs.

@laughingman7743
Copy link
Member Author

laughingman7743 commented Jan 5, 2020

TODO:

  • Impl executemany with PandasCursor.
  • Update README.

@laughingman7743 laughingman7743 force-pushed the pnadas_to_sql branch 6 times, most recently from 2a869aa to b1e2097 Compare January 13, 2020 06:19
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.

1 participant