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

support SET <col> = <expr>, ... clause in LOAD DATA #2653

Merged
merged 17 commits into from
Sep 10, 2024
Merged

support SET <col> = <expr>, ... clause in LOAD DATA #2653

merged 17 commits into from
Sep 10, 2024

Conversation

jycor
Copy link
Contributor

@jycor jycor commented Sep 9, 2024

partial support for: dolthub/dolt#8307

Copy link
Contributor

@fulghum fulghum left a comment

Choose a reason for hiding this comment

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

The initial support for the SET clause looks good, but I don't think it's enough to resolve the customer's issue. In their LOAD DATA statement, they are using a feature where they load some of the input file's fields into user vars and then reference those user var in the SET clause to set other columns.

It seems like the SET expression to set the column's value would work already, but I don't think we support loading the values into user vars yet. Either way, we should add tests to cover that use case.

I can approve this one if you want to take it in two steps, otherwise I can take another look at this one after you add in the user var support.

@jycor jycor merged commit 01d3c5f into main Sep 10, 2024
8 checks passed
@jycor jycor deleted the james/load branch September 10, 2024 18:44
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.

2 participants