8000 DROP of missing entry should fail in binding by jeewonhh · Pull Request #17474 · duckdb/duckdb · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

DROP of missing entry should fail in binding #17474

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

Merged
merged 1 commit into from
May 14, 2025
Merged

Conversation

jeewonhh
Copy link
Contributor

DROP statements should fail during bind if we fail to find an entry. Only DROP <CATALOG TYPE> IF NOT EXISTS statements should be tolerant to missing entries.

@Mytherin Mytherin merged commit 4bf6e76 into duckdb:main May 14, 2025
47 of 48 checks passed
@Mytherin
Copy link
Collaborator

Thanks!

krlmlr added a commit to duckdb/duckdb-r that referenced this pull request May 18, 2025
DROP of missing entry should fail in binding (duckdb/duckdb#17474)
add regression_threshold_seconds argument to `regression/test_runner.py` (duckdb/duckdb#17485)
krlmlr added a commit to duckdb/duckdb-r that referenced this pull request May 19, 2025
DROP of missing entry should fail in binding (duckdb/duckdb#17474)
add regression_threshold_seconds argument to `regression/test_runner.py` (duckdb/duckdb#17485)
krlmlr added a commit to duckdb/duckdb-r that referenced this pull request May 19, 2025
DROP of missing entry should fail in binding (duckdb/duckdb#17474)
add regression_threshold_seconds argument to `regression/test_runner.py` (duckdb/duckdb#17485)
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
0