Skip to content

Conversation

@alpaylan
Copy link
Contributor

@alpaylan alpaylan commented Oct 8, 2025

No description provided.

/// Table not found in get_collseq_from_expr
#[error("table not found")]
TableNotFound,
/// Column not found in get_collseq_from_expr
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why is this specific to get_collseq_from_expr? Should we rename this to NoSuchColumn and return it for all the no such column errors?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

A part of this was that I was scared of breaking any compatibility so I kept every error letter by letter, that's why some errors aren't deduplicated properly I think. It makes sense to me that we merge NoSuchColumn for all no such column errors.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Got it - I'd say don't worry about it, if the tests pass then we're good. Let's not get those fears get in the way of improving the codebase 👍 we're still 0.x after all, i would be surprised if end users were already relying on specific error messages

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll make some more updates to consolidate some errors even more, after that we should be good to merge I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants