Bug #109355 NULL Tinyint exported as 0
Submitted: 13 Dec 2022 6:58 Modified: 22 Dec 2022 12:56
Reporter: Jose Maria Calero Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.18 OS:Windows (Microsoft Windows 10 Pro)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[13 Dec 2022 6:58] Jose Maria Calero
This bug appears when you have executed any query over a table that has a TINYINT that can be NULL. Let us assume there are rows with all the possible values, i.e. 0, 1 and NULL. The results in screen are correct. However, when you export such results in Excel XML and open them in Excel, you will inmediately see how all the NULL values have been replaced by 0s making an inconsistent version of the Excel file with respect to the data available in the DB.  

How to repeat:
Already indicated in the description

Suggested fix:
NULLs for TINYINT should be expored as NULL like any other data type.
[22 Dec 2022 12:56] MySQL Verification Team
Hello Jose,

Thank you for the bug report.
I tried to reproduce your issue on windows 10 with workbench 8.0.31 using dummy table having tinyint column and exported to excel but I am not seeing any issues at my end. Please try latest version i.e 8.0.31. Thanks.

Ashwini Patil
[22 Dec 2022 12:56] MySQL Verification Team
8.0.31 test results

Attachment: 109355_test_results.docx (application/vnd.openxmlformats-officedocument.wordprocessingml.document, text), 186.73 KiB.