Date column UI component not functional with mysql type date, only compatible with datetime when date is empty in database (0000-00-00)

[sezio]

Preconditions and environment

• Magento version : 2.4.2-p1

Steps to reproduce

1. Create a table with a date field in a db_schema.xml :

    <table name="test_table" resource="default" engine="innodb" comment="Test table">
        <column xsi:type="int" name="id" unsigned="true" nullable="false" identity="true" comment="Row ID"/>
        <column xsi:type="date" name="test_date" nullable="true" comment="Test date"/>
    </table>

2. Create a new grid in backend with a column configured as follow :

        <column name="test_date" class="Magento\Ui\Component\Listing\Columns\Date" component="Magento_Ui/js/grid/columns/date" sortOrder="40">
            <settings>
                <filter>dateRange</filter>
                <dataType>date</dataType>
                <dateFormat>MMM d, YYYY</dateFormat>
                <label translate="true">My Date</label>
            </settings>
        </column>

3. Insert a row in your table with the date value set to "0000-00-00" :
   insert into test_table(test_date) values("0000-00-00");

4. Display your grid

Expected result

When displayed, the date column should not display any date as this is not a valid date.

Actual result

Magento calculates a date to "-0001-11-30 00:09:21" in \Magento\Ui\Component\Listing\Columns\Date::prepareDataSource

Additional information

The condition in \Magento\Ui\Component\Listing\Columns\Date::prepareDataSource to prevent a bad calculation of a datetime initialized to "0000-00-00 00:00:00" is the following :

                if (isset($item[$this->getData('name')])
                    && $item[$this->getData('name')] !== "0000-00-00 00:00:00"
                ) {
                    ...
                }

Therefore, it is strictly compatible with a datetime field and not with a date field.
To make it compatible with a date field, it should be something like :

                if (isset($item[$this->getData('name')])
                    && $item[$this->getData('name')] !== "0000-00-00 00:00:00"
                    && $item[$this->getData('name')] !== "0000-00-00"
                ) {
                    ...
                }

Also, Firefox won't display this date at all while Chrome displays it as the 11th january of 2030 :
Firefox :

Brave (also reproductible on chrome) :

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @sezio. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Lima. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Lima]

Hi @sezio,
Thank you for the collaboration and reporting the issue.

Tried reproducing the issue on latest 2.4-develop instance and the issue is reproducible for us.

Steps followed to reproduce the issue:-

1. Install latest 2.4-develop instance
2. Create a custom table

<table name="test_table" resource="default" engine="innodb" comment="Test table">
        <column xsi:type="int" name="id" unsigned="true" nullable="false" identity="true" comment="Row ID"/>
        <column xsi:type="date" name="test_date" nullable="true" comment="Test date"/>
    </table>

3. Create a new grid in backend with a column configured as follows

 <column name="test_date" class="Magento\Ui\Component\Listing\Columns\Date" component="Magento_Ui/js/grid/columns/date" sortOrder="40">
            <settings>
                <filter>dateRange</filter>
                <dataType>date</dataType>
                <dateFormat>MMM d, YYYY</dateFormat>
                <label translate="true">My Date</label>
            </settings>
        </column>

4. Insert into database : insert into test_table(test_date) values("0000-00-00");

Output:
Invalid date is displayed

Screenshots:

Based on above information I am confirming the issue.

Thanks