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 broken error messages for type mismatches in a number of schema objects #8294

Merged
merged 1 commit into from
Feb 4, 2025

Conversation

msullivan
Copy link
Member

Currently, for triggers, access policies, and function argument
defaults, if the inferred type is something that doesn't appear in the
schema (like a tuple), we a "cannot get item data" error.

Fix that by using the schemas generated while compiling the expressions.

Fixes #8291.

@msullivan msullivan added the to-backport-6.x PRs that *should* be backported to 6.x label Feb 4, 2025
…bjects

Currently, for triggers, access policies, and function argument
defaults, if the inferred type is something that doesn't appear in the
schema (like a tuple), we a "cannot get item data" error.

Fix that by using the schemas generated while compiling the expressions.

Fixes #8291.
@msullivan msullivan force-pushed the type-mismatch-schemas branch from 1bd85f9 to a6c280d Compare February 4, 2025 04:47
@msullivan msullivan merged commit 7945efe into master Feb 4, 2025
23 checks passed
@msullivan msullivan deleted the type-mismatch-schemas branch February 4, 2025 18:12
@msullivan msullivan added backported-6.x PRs that *have* been backported to 6.x and removed to-backport-6.x PRs that *should* be backported to 6.x labels Feb 4, 2025
msullivan added a commit that referenced this pull request Feb 4, 2025
…bjects (#8294)

Currently, for triggers, access policies, and function argument
defaults, if the inferred type is something that doesn't appear in the
schema (like a tuple), we a "cannot get item data" error.

Fix that by using the schemas generated while compiling the expressions.

Fixes #8291.
msullivan added a commit that referenced this pull request Feb 4, 2025
…bjects (#8294)

Currently, for triggers, access policies, and function argument
defaults, if the inferred type is something that doesn't appear in the
schema (like a tuple), we a "cannot get item data" error.

Fix that by using the schemas generated while compiling the expressions.

Fixes #8291.
deepbuzin pushed a commit that referenced this pull request Feb 18, 2025
…bjects (#8294)

Currently, for triggers, access policies, and function argument
defaults, if the inferred type is something that doesn't appear in the
schema (like a tuple), we a "cannot get item data" error.

Fix that by using the schemas generated while compiling the expressions.

Fixes #8291.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backported-6.x PRs that *have* been backported to 6.x
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6.x migration regression? - item not present in schema
3 participants