Skip to content

Conversation

@facetosea
Copy link
Contributor

Description

Please briefly describe the code changes in this pull request.

Checklist

Please check the items in the checklist if applicable.

  • Is the user manual updated?
  • Are the test cases passed and automated?
  • Is there no significant decrease in test coverage?

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @facetosea, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a bug in the decimal conversion logic where string-based data types like NCHAR, VARCHAR, and VARBINARY were not being correctly converted to DECIMAL due to an erroneous length calculation. The fix involves adjusting the length parameter passed during the conversion. Additionally, comprehensive test cases have been added to ensure the robustness and accuracy of decimal-to-NCHAR conversions across different precision and scale settings.

Highlights

  • Decimal Conversion Fix: Corrected an error in the decimal##FromStr macro where VARSTR_HEADER_SIZE was incorrectly subtracted from the input string length for NCHAR, VARCHAR, and VARBINARY types, leading to potential conversion issues when casting these types to DECIMAL.
  • New Test Cases: Introduced a new test method constValToDecimal in test_datatype_decimal.py to thoroughly validate the conversion of constant decimal values to NCHAR, covering various precision, scale, and rounding scenarios.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request aims to fix an error when converting NCHAR data to DECIMAL. The fix in decimal.c adjusts the string length used in the conversion, which seems correct for NCHAR. However, this change also affects VARCHAR and VARBINARY types, and it's important to verify that this is intended and does not cause regressions. I've added a comment regarding this. The Python test file introduces new tests, but they seem to test DECIMAL to NCHAR conversion, not the NCHAR to DECIMAL path that was fixed. I've provided suggestions to add a more appropriate test case to validate the fix. Additionally, I found a duplicated test case that should be removed for better maintainability.

@guanshengliang guanshengliang merged commit d6db7b7 into main Nov 11, 2025
9 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants