Skip to content

Conversation

@hadley
Copy link
Member

@hadley hadley commented Dec 3, 2025

This seems like it should be safe, since there's no ambiguity when there's only a single table, and that's what lazy_select_query represents.

Fixes #1577. Fixes #1485. Fixes #1482.

@mgirlich do you have time to review a few dbplyr PRs?

This seems like it should be safe, since there's no ambiguity when there's only a single table, and that's what `lazy_select_query` represents.

Fixes #1577. Fixes #1485.
@hadley hadley requested a review from mgirlich December 3, 2025 15:38
@mgirlich
Copy link
Collaborator

mgirlich commented Dec 5, 2025

I should find some time for reviews. I'm not very deep into R or dbplyr at the moment but it still looks familiar enough 😄
The change seems simple and logical but it just shows the unfortunate situation of SQL. Always qualifying with * was introduced to fix some issues: #1003 and #908. So this change would probably break compatibility with Oracle and Teradata. It seems we need to make this backend-specific.

@hadley
Copy link
Member Author

hadley commented Dec 5, 2025

Oooh good memory. I'll make it optional and only enable for Oracle and teradata.

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.

Adding filter creates a qualified select * which causes error sql in in_catalog breaks with filter head() modifies SELECT *

3 participants