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

Clarify messaging for column not found #832

Merged
merged 1 commit into from
Dec 15, 2024
Merged

Conversation

thadguidry
Copy link
Collaborator

  • Because this is prefixed in the "detail" field output with "Failed to parse RQL - " then saying "missing" makes it seem like RQL had some problem parsing, when in fact, RQL had no problem at all, it was the DB that could not find a column. It's better to say "not found" instead of "missing".

- Because this is prefixed in the "detail" field output with "Failed to parse RQL - " then saying "missing" makes it seem like RQL had some problem.  It's better to say "not found" instead of "missing".
@thadguidry thadguidry added the enhancement New feature or request label Dec 14, 2024
@thadguidry thadguidry requested a review from kdhrubo December 14, 2024 03:18
Copy link
Collaborator

@kdhrubo kdhrubo left a comment

Choose a reason for hiding this comment

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

Lets retest , the rollup of exception may be causing this trouble.

@kdhrubo kdhrubo merged commit 0615016 into master Dec 15, 2024
1 of 2 checks passed
@kdhrubo kdhrubo deleted the thadguidry-patch-1 branch December 15, 2024 05:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants