Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: refactor sql onto separate connector #39

Merged
merged 4 commits into from
Jun 7, 2023

Conversation

kgpayne
Copy link
Collaborator

@kgpayne kgpayne commented Jun 5, 2023

No description provided.

@kgpayne kgpayne marked this pull request as ready for review June 5, 2023 21:05
Copy link
Contributor

@pnadolny13 pnadolny13 left a comment

Choose a reason for hiding this comment

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

@kgpayne this looks great to me!

I think my tests PR is in a pretty good place so optionally that could be a nice way to double check everything still passes here.

@kgpayne kgpayne self-assigned this Jun 7, 2023
@kgpayne kgpayne merged commit e3764cd into main Jun 7, 2023
@kgpayne kgpayne deleted the kgpayne/refactor-sql-onto-connector branch June 7, 2023 15:18
pnadolny13 added a commit that referenced this pull request Jun 8, 2023
Closes #43

It turns out that this test had been fixed by other changes. I suspect
it was part of #39.
Previously I had implemented a way to cache table properties but I
suspect that the cache was not being invalidated when the schema updated
so it was attempting to recreate an existing column since it didnt find
it in the cache.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants