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.

Sign up for GitHub

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

Jump to bottom

Confusing "Bare" in doesn't exist messages #4571

Closed
alamb opened this issue Dec 9, 2022 · 0 comments · Fixed by #4572
Closed

Confusing "Bare" in doesn't exist messages #4571

alamb opened this issue Dec 9, 2022 · 0 comments · Fixed by #4572
Assignees
@alamb
Labels
bug Something isn't working

Comments

@alamb
Copy link
Contributor

alamb commented Dec 9, 2022

Describe the bug

I think #4530 made error messages look much crappier. For example:

Table Bare \{ table: "user" \} doesn't exist.

I noticed this while adding errors in #4535

To Reproduce
See tests in #4535

Expected behavior
I would like the messages to only have the table name (not the Debug version of OwnedTableReference).

Additional context
Add any other context about the problem here.
@alamb alamb added the bug Something isn't working label Dec 9, 2022
@alamb alamb self-assigned this Dec 9, 2022
@alamb alamb mentioned this issue Dec 9, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alamb alamb

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove Confusing "Bare" in does not exist messages alamb/datafusion
1 participant
@alamb