Skip to content

Align DateStyle parsing with PostgreSQL#5144

Merged
renecannao merged 2 commits intov3.0from
v3.0_datestyle-parser-tweak
Oct 14, 2025
Merged

Align DateStyle parsing with PostgreSQL#5144
renecannao merged 2 commits intov3.0from
v3.0_datestyle-parser-tweak

Conversation

@rahim-kanji
Copy link
Collaborator

@rahim-kanji rahim-kanji commented Oct 4, 2025

Updated PgSQL_DateStyle_Util::parse_datestyle() to support prefix-based matching for known tokens (POSTGRES, EURO, NONEURO). This allows variants like "PostgreSQL" and "European" to be recognized as valid inputs. The change improves compatibility and consistency with PostgreSQL’s DateStyle parsing behavior.

PostgreSQL is treated the same as POSTGRES, EURO/EUROPEAN map to DMY, and NONEURO/US map to MDY

Updated PgSQL_DateStyle_Util::parse_datestyle() to support prefix-based
matching for known tokens (POSTGRES, EURO, NONEURO). This allows variants
like "PostgreSQL", "European", to be recognized as valid inputs.
@gemini-code-assist
Copy link

Summary of Changes

Hello @rahim-kanji, 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 enhances the PgSQL_DateStyle_Util::parse_datestyle() function to accept more flexible inputs for DateStyle parameters. By implementing prefix-based matching for key tokens like "POSTGRES", "EURO", and "NONEURO", the system now better aligns with PostgreSQL's native parsing behavior, allowing for variations such as "PostgreSQL" or "European" to be correctly recognized. This improves compatibility and robustness when setting DateStyle.

Highlights

  • Enhanced DateStyle Parsing: The PgSQL_DateStyle_Util::parse_datestyle() function now supports prefix-based matching for POSTGRES, EURO, and NONEURO tokens, allowing for more flexible input variations like "PostgreSQL" or "European".
  • Improved Compatibility: This change aligns the DateStyle parsing behavior more closely with PostgreSQL's native parsing, improving overall compatibility and robustness when handling date style settings.
  • New Test Cases: Additional test cases have been introduced to validate the new prefix-based matching for DateStyle parameters, ensuring the updated parsing logic works as expected with various input formats.
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.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Oct 4, 2025

Copy link

@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 correctly aligns the DateStyle parsing with PostgreSQL's prefix-matching behavior for keywords like POSTGRES, EURO, and NONEURO. The changes are implemented using strncasecmp which is appropriate for case-insensitive prefix comparison. The addition of test cases in pgsql-set_parameter_validation_test-t.cpp is great and ensures the new functionality is well-tested.

My feedback focuses on a minor stylistic improvement to make the code more idiomatic to modern C++, by replacing the C-style sizeof("LITERAL") - 1 with std::string_view("LITERAL").length() for getting the length of string literals. This improves readability without any performance cost.

@renecannao renecannao merged commit 42f6d9d into v3.0 Oct 14, 2025
5 of 6 checks passed
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.

2 participants