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

Lambda argument resolution in alter table #11607

Closed
2 tasks done
eaubin opened this issue Apr 10, 2024 · 0 comments · Fixed by #11976
Closed
2 tasks done

Lambda argument resolution in alter table #11607

eaubin opened this issue Apr 10, 2024 · 0 comments · Fixed by #11976

Comments

@eaubin
Copy link

eaubin commented Apr 10, 2024

What happens?

In a alter column using with a lambda, a reference to a lambda bound variable is attempted to be resolved as column reference.

To Reproduce

CREATE TABLE Cities AS SELECT * FROM (VALUES ('Amsterdam', [90,10]), ('London', [89,102])) Cities(Name, Prices);

ALTER TABLE Cities ADD COLUMN LowPrices INTEGER[];

ALTER TABLE Cities
ALTER COLUMN LowPrices SET DATA TYPE INTEGER[] USING 
list_filter(Cities.Prices, price -> price<100);
Binder Error: Table does not contain column price referenced in alter statement!

OS:

osx arm64

DuckDB Version:

0.10.2-dev311

DuckDB Client:

Python

Full Name:

eaubin

Affiliation:

NA

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have tested with a nightly build

Did you include all relevant data sets for reproducing the issue?

Yes

Did you include all code required to reproduce the issue?

  • Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

  • Yes, I have
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants