Skip to content

Resolve PostgreSQL custom parameter types using schema metadata#39225

Open
somiljain2006 wants to merge 6 commits into
apache:masterfrom
somiljain2006:Custom-type-handling
Open

Resolve PostgreSQL custom parameter types using schema metadata#39225
somiljain2006 wants to merge 6 commits into
apache:masterfrom
somiljain2006:Custom-type-handling

Conversation

@somiljain2006

@somiljain2006 somiljain2006 commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Fixes #36978

Add a schema metadata fallback for PostgreSQL prepared statement parameter type resolution, populate unresolved PGobject types, support custom PostgreSQL types when JDBC metadata is unavailable, and extend parameter-to-column resolution for INSERT and UPDATE statements.


Before committing this PR, I'm sure that I have checked the following options:

  • My code follows the code of conduct of this project.
  • I have self-reviewed the commit code.
  • I have (or in the comment I request) added corresponding labels for the pull request.
  • I have passed Maven check locally: ./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e.
  • I have made corresponding changes to the documentation.
  • I have added corresponding unit tests for my changes.
  • I have updated the Release Notes of the current development version. For more details, see Update Release Note

@somiljain2006

Copy link
Copy Markdown
Contributor Author

@terrymanu Can you review this pr? The remaining 2 CI failures (MCP conformance test suite and the HiveConnectionPropertiesParser SPI issue) are unrelated to these changes.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PostgreSQL Custom Types Parsing Issue in ShardingSphere-Proxy

1 participant