Use auto_create_table when writing
#59
Open
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.
In #56 we added a
pandas<2.2restriction due topandas=2.2only supportingsqlalchemy>=2, butsnowflake-sqlalchemyrequiringsqlalchemy<2. This is unfortunate, but better than things breaking with the latestpandasrelease.I noticed that we're only using
snowflake-sqlalchemyto auto-create a table if it doesn't exist andsnowflake-connector-python >= 2.7.3has aauto_create_table=keyword for this exact functionality. This PR uses the built inauto_create_table=Truein snowflake and removes our dependency onsnowflake-sqlalchemyaltogether. This also let's us drop thepandas<2.2restriction.