Postgres copy explicates columns and column order #1137
Merged
Conversation
This file contains 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
austinweisgrau
force-pushed
the
pg_copy
branch
2 times, most recently
from
a858cc0 to
ba56c50
Compare
austinweisgrau
force-pushed
the
pg_copy
branch
3 times, most recently
from
cfc231a to
5587233
Compare
|
Also now includes a couple other changes that make the Postgres query methods more robust:
|
Necessary in certain situations, e.g. table name has capital letters
Some tables have uppercase letters in their name
Some postgres columns (e.g. if they have a capital letter) need to be surrounded by double quotes
without this change, the query fails to parse
austinweisgrau
force-pushed
the
pg_copy
branch
from
5587233 to
b9d6d45
Compare
shaunagm
approved these changes
Oct 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Without this change, the Postgres copy method only works if the Table has the same columns in the same order as the destination table. With this change, the source table can have a subset of columns in a different order but still successfully load to the destination table.