Bug #106434 table cannot be loaded if the time field value is over the 24:00 on Win/Ubuntu
Submitted: 10 Feb 2022 13:47 Modified: 4 Apr 2022 9:34
Reporter: David Chien Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / ODBC Severity:S1 (Critical)
Version:8.0.28, 8.0.27, 8.0.26... OS:Linux (Ubuntu 18.04.6 LTS & Windows 2019)
Assigned to: CPU Architecture:x86

[10 Feb 2022 13:47] David Chien
Description:
Hi,

My clients and I, we recently encountered an issue regards to load up a time field column from a external data table from MySQL Database via MySQL ODBC connector.

If I tried to load up the time field table with the ODBC connector/driver version that belongs to version 5.2.7, then it can loads up properly.

But if I load up the ODBC connector/driver version that belongs to the newer version like 8.0.28, 8.0.27, 8.0.26 and so on, then I am not able to open the table and I got an error with...it says time format is invalid.

The time field data consists with the working hour duration time that we required over the 24:00, the data can shows normally if we use the 5.2.7 version driver, but other than this, we are not able to see the data and got error message.

Could you please advise or provide a fix to this issue, since we are not willing to downgrade our ODBC driver version to 5.2.7.

P.S. Please refer to the screenshot for reference, and the data is provided to reproduced the issue.

How to repeat:
1. Ubuntu/Windows OS is ready.

2. Setup ODBC connector/driver properly, with the newest version (8.0.28, 8.0.27, or 8.0.26...so on)

3. Have MySQL Database ready with the provided sql data file. (Must contain the time field with the time value over the 24:00)

4. Use LibreBase load up the data from MySQL database, or use MS Excel load up the data from MySQL database with the ODBC connector/driver (8.0.28)

5. Cannot open up the table and generate an error states that the time field format is invalid, which is not happening if the driver version is 5.2.7.

Suggested fix:
Please make the new version of odbc driver that can work as the same way as 5.2.7 or remove the error to help us to display the working hour data properly.
[10 Feb 2022 15:41] David Chien
Actually, FileMaker Pro also got effected by the odbc driver on windows and ubuntu, as long as if it used the mysql odic driver, the data will be affected.
[30 Mar 2022 13:18] MySQL Verification Team
Hello David Chien,

Thank you for the bug report.
I tried to reproduce your issue on windows 10/Ubuntu 20.04 with MS Excel/LibreBase with the sql file attached but I am not seeing any issues at my end.

Regards,
Ashwini Patil
[4 Apr 2022 9:34] David Chien
hi Ashwini Patil,

Thank you for replying me,

May I ask few questions from you?

what version of your odbc driver do you use?

because if you use the newer ODBC version driver, you should have an issue from loading up the data table while importing external data table via odbc.

Could you please provide your odbc version number?

and how do you load your external data to your ms excel or libre office?

Could you please double check that you actually loaded the data by using the MySQL odbc driver?

if not by odbc driver, the issue will not be able to reproduced.

thanks!

David
[4 Apr 2022 12:49] MySQL Verification Team
Hello David Chien,

I've tried to reproduce your issue again on windows 10 with Connector / ODBC 8.0.28 but I am not seeing any issues at my end. Please find answers below.

what version of your odbc driver do you use?
I used Connector / ODBC 8.0.28

and how do you load your external data to your ms excel or libre office?
Loaded data on clinking Get External Data->From Other Source->From Data Connection Wizard->ODBC DSN->saved MySQL ODBC data source->Select Database and Tables
No error prompted and data loaded successfully.

Regards,
Ashwini Patil