Conversation
|
@ml-mave is attempting to deploy a commit to the Adel Salakh's projects Team on Vercel. A member of the Team first needs to authorize it. |
This was referenced Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #503, fixes #594
The problem is that when PostgreSQL is queried for query types, it "resolves" domain types, meaning it only returns the base type.
The fix is to check if the result column is a direct column reference, and if so, we just query the column type from the pg_attribute table.
This PR currently does not have tests unfortunately. We've confirmed this fix works in our fork, though.
@blahbleepew @antoineharel @pnispel If you have time to check whether this PR fixes your issue, that would be great.