Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-38584

TO_DATE: NLS_DATE_LANGUAGE=VIETNAMESE does not parse values which work in Oracle

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • N/A
    • 12.3.1
    • Server
    • None
    • Not for Release Notes
    • Fixed by retrying matching of months with 2 words

    Description

      The one-line test case is also attached as a file, in case JIRA corrupts the string.

      Oracle

      SELECT TO_DATE('15 tháng tư 2024','DD MONTH YYYY','NLS_DATE_LANGUAGE=VIETNAMESE') AS x FROM DUAL;
       
      X
      15-APR-24
      

      bb-12.3-MDEV-19683-to_date f45636ea81a5a02444833e993e47c262ed52f384

      MariaDB [test]> SELECT TO_DATE('15 tháng tư 2024','DD MONTH YYYY','NLS_DATE_LANGUAGE=VIETNAMESE') AS x FROM DUAL;
      +------+
      | x    |
      +------+
      | NULL |
      +------+
      1 row in set, 1 warning (0.001 sec)
       
      MariaDB [test]> show warnings;
      +---------+------+---------------------------------------------------------------------+
      | Level   | Code | Message                                                             |
      +---------+------+---------------------------------------------------------------------+
      | Warning | 1411 | Incorrect datetime value: '15 tháng tư 2024' for function to_date   |
      +---------+------+---------------------------------------------------------------------+
      1 row in set (0.000 sec)
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.