Alena0704 opened a new pull request, #1873:
URL: https://github.com/apache/cloudberry/pull/1873

   Feature: add TRY_CONVERT extension
   
   TRY_CONVERT(source_value, default_value) casts source_value to the type of 
default_value and returns default_value whenever the cast fails, which is the 
behaviour of TRY_CAST in SQL Server. Without it a single malformed value makes 
the whole query fail, and the plpgsql workarounds that catch the error per row 
are several times slower.
   
   TRY_CONVERT('42'::text, NULL::int2)   -- returns 42::int2
   TRY_CONVERT('42d'::text, NULL::int2)  -- returns NULL::int2
   TRY_CONVERT('42d'::text, 1234::int2)  -- returns 1234::int2
   
   The conversion to use is resolved the same way the parser resolves an 
explicit cast in coerce_type(): a pg_cast entry, an I/O conversion or a 
binary-compatible relabel, followed by the length coercion of the target type. 
Casts between array types and casts to domain types are not supported and are 
reported as query errors, the same as a cast that does not exist at all; only a 
failure caused by the converted data is turned into the default value.
   
   The cast itself runs inside a PG_TRY() block, since the datatype input 
functions of Cloudberry cannot yet report a conversion failure without throwing.
   
   The extension is marked trusted, so the owner of a database can install it 
without being a superuser.
   
   Co-authored-by: Vladimir Rachkin [[email protected]](mailto:[email protected])
   See: PR#901 https://github.com/apache/cloudberry/pull/901
   
   
   See: PR#901 <https://github.com/apache/cloudberry/pull/901>
   
   <!-- Thank you for your contribution to Apache Cloudberry (Incubating)! -->
   
   Fixes #ISSUE_Number
   
   ### What does this PR do?
   <!-- Brief overview of the changes, including any major features or fixes -->
   
   ### Type of Change
   - [ ] Bug fix (non-breaking change)
   - [ ] New feature (non-breaking change)
   - [ ] Breaking change (fix or feature with breaking changes)
   - [ ] Documentation update
   
   ### Breaking Changes
   <!-- Remove if not applicable. If yes, explain impact and migration path -->
   
   ### Test Plan
   <!-- How did you test these changes? -->
   - [ ] Unit tests added/updated
   - [ ] Integration tests added/updated
   - [ ] Passed `make installcheck`
   - [ ] Passed `make -C src/test installcheck-cbdb-parallel`
   
   ### Impact
   <!-- Remove sections that don't apply -->
   **Performance:**
   <!-- Any performance implications? -->
   
   **User-facing changes:**
   <!-- Any changes visible to users? -->
   
   **Dependencies:**
   <!-- New dependencies or version changes? -->
   
   ### Checklist
   - [ ] Followed [contribution 
guide](https://cloudberry.apache.org/contribute/code)
   - [ ] Added/updated documentation
   - [ ] Reviewed code for security implications
   - [ ] This PR contains AI-assisted code generation
   - [ ] Requested review from [cloudberry 
committers](https://github.com/orgs/apache/teams/cloudberry-committers)
   
   ### Additional Context
   <!-- Any other information that would help reviewers? Remove if none -->
   
   ### CI Skip Instructions
   <!--
   To skip CI builds, add the appropriate CI skip identifier to your PR title.
   The identifier must:
   - Be in square brackets []
   - Include the word "ci" and either "skip" or "no"
   - Only use for documentation-only changes or when absolutely necessary
   -->
   
   ---
   <!-- Join our community:
   - Mailing list: 
[[email protected]](https://lists.apache.org/[email protected])
 (subscribe: [email protected])
   - Discussions: https://github.com/apache/cloudberry/discussions -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to