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

Fix failure when check constraint is null #20906

Merged
merged 1 commit into from
Mar 1, 2024

Conversation

martint
Copy link
Member

@martint martint commented Mar 1, 2024

The planner was incorrectly trying to derive the necessary coercions based on the rewritten expression instead of the original one.

Release notes

(x) Release notes are required, with the following suggested text:

# General
* Fix query failure when CHECK constraint is null. ({issue}`issuenumber`)

The planner was incorrectly trying to derive the necessary
coercions based on the rewritten expression instead of the
original one.
@cla-bot cla-bot bot added the cla-signed label Mar 1, 2024
@martint martint requested a review from ebyhr March 1, 2024 20:23
@martint martint merged commit a3d1fe8 into trinodb:master Mar 1, 2024
92 checks passed
@martint martint deleted the null-constraint branch March 1, 2024 21:23
@github-actions github-actions bot added this to the 440 milestone Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants