Bug #121640 MySQL Workbench 26.10.0 displays DATETIME and TIMESTAMP values as date only in Result Grid
Description:
Possibly related to Bug #115709.
DATETIME and TIMESTAMP values are displayed as dates only in the Result Grid of MySQL Workbench 26.10.0.
The database returns valid datetime values including time information, but the Result Grid displays only the date portion.
The issue affects:
- NOW()
- CURRENT_TIMESTAMP()
- DATETIME columns
- TIMESTAMP columns
Casting the values to CHAR displays the correct datetime value including the time portion.
This makes it difficult to inspect DATETIME/TIMESTAMP values using common queries such as:
SELECT * FROM table_name;
How to repeat:
1. Execute:
SELECT NOW();
Actual result:
2026/10/30
Expected result:
2026-10-30 HH:MM:SS
2. Execute:
SELECT CURRENT_TIMESTAMP();
Actual result:
2026/10/30
Expected result:
2026-10-30 HH:MM:SS
3. Execute:
SELECT NOW() AS dt,
CAST(NOW() AS CHAR) AS dt_char;
Actual result:
dt = 2026/10/30
dt_char = 2026-10-30 16:17:07
The Result Grid displays only the date portion for the DATETIME value, while the same value cast to CHAR includes the full date and time.
4. Verify a DATETIME column:
SHOW COLUMNS
FROM reservation
LIKE 'updated_at';
Result:
Type = datetime
5. Execute:
SELECT updated_at
FROM reservation
LIMIT 1;
Actual result:
2020/06/01
Observed behavior:
Only the date portion is displayed in the Result Grid although the column type is DATETIME.
Suggested fix:
Display DATETIME and TIMESTAMP values with their full date and time component in the Result Grid, or provide a user-configurable display format option.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.038 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.