| Bug #111648 | Dates With 0 year causing issue when we retrieving | ||
|---|---|---|---|
| Submitted: | 4 Jul 2023 3:37 | Modified: | 5 Nov 2023 12:23 |
| Reporter: | krishna prasad | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Connectors: Document Store: DevAPI | Severity: | S3 (Non-critical) |
| Version: | 8 | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[5 Oct 2023 12:23]
MySQL Verification Team
Hello krishna Prasad, Thank you for the bug report. Could you please provide repeatable test case(exact steps, sample project, etc. - please make it as private if you prefer) to reproduce this issue at our end? Thanks. Regards, Ashwini Patil
[6 Nov 2023 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
Description: When we insert the Date in MYSQL Server there are certain modes to check invalid dates, such as NO_ZERO_DATE_MODE which does not allow 0000-00-00 and NO_ZERO_IN_DATE which does not allow 0001-00-00, but there is no mode which does not allow 0000-01-01. How to repeat: Easily reproduacable, insert DATE in Date Column 0000-01-01, Fetch the date with JDBC Connector resultset.getObject("Date")