Bug #90355 Querying 0 timestamp values throws error

Submitted: 9 Apr 2018 20:33 Modified: 25 Apr 2018 13:34
Reporter: Alfredo Kojima Email Updates:
Status: Closed Impact on me:
None 
Category:Shell General / Core Client Severity:S3 (Non-critical)
Version:8.0.11 OS:Any
Assigned to: CPU Architecture:Any

[9 Apr 2018 20:33] Alfredo Kojima 
Description:
Querying 0 timestamp values throws an exception, regardless of classic or x protocol.

How to repeat:

select LAST_ERROR_TIMESTAMP from performance_schema.replication_connection_status;
ERROR: ClassicResult.fetchOne: Valid month range is 1-12
[25 Apr 2018 13:34] Margaret Fisher 
Posted by developer:
 
Changelog entry added for MySQL Shell 8.0.12:
MySQL Shell returned an error when querying timestamp values that were zero, because a zero value for the month or day in a date was not accepted. Zero timestamp values can now be used without producing an error.
[17 May 2018 15:31] MySQL Verification Team 
Bug #90918 marked as duplicate of this one

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.