Bug #78917 | Connector modifies result type after parent tinyint value is null | ||
---|---|---|---|
Submitted: | 22 Oct 2015 8:01 | Modified: | 1 Jun 2018 21:44 |
Reporter: | Florian Jäcksch | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / NET | Severity: | S3 (Non-critical) |
Version: | 6.9.7 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[22 Oct 2015 8:01]
Florian Jäcksch
[27 Oct 2015 6:02]
Chiranjeevi Battula
Hello Florian Jäcksch, Thank you for the bug report and test case. Verified this behavior on Visual Studio 2013 (C#.Net) with MySQL Connector/Net 6.9.7. Thanks, Chiranjeevi
[27 Oct 2015 6:03]
Chiranjeevi Battula
screenshot
Attachment: 78917.PNG (image/png, text), 52.87 KiB.
[10 Nov 2015 10:03]
Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=79196 marked as duplicate of this one.
[23 Aug 2016 13:36]
Takuya Sakurai
I found this bug is caused by MySqlByte.ReadValue. If the value is null, it creates a new MySqlByte instance without copying TreatAsBoolean property.
[26 Dec 2017 13:02]
Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=89040 marked as duplicate of this one.
[28 Mar 2018 13:55]
OCA Admin
Contribution submitted via Github - Bug #78917 - Remember whether TINYINT was treated as boolean (*) Contribution by David Warner (Github Quppa, mysql-connector-net/pull/20#issuecomment-376872111): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: git_patch_176963190.txt (text/plain), 1.92 KiB.
[1 Jun 2018 21:44]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL Connector/NET 6.10.8 release, and here's the changelog entry: All columns of type TINYINT(1) stopped returning the expected Boolean value after the connector encountered a NULL value in any column of this type. Thanks to David Warner for the patch. Thank you for the bug report.