Bug #101252 | Can't query CHAR(36) column containing NULL | ||
---|---|---|---|
Submitted: | 20 Oct 2020 20:09 | Modified: | 27 Jan 2021 18:56 |
Reporter: | Bradley Grainger (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / NET | Severity: | S2 (Serious) |
Version: | 8.0.22 | OS: | Windows (10) |
Assigned to: | CPU Architecture: | Any | |
Tags: | regression |
[20 Oct 2020 20:09]
Bradley Grainger
[21 Oct 2020 5:52]
MySQL Verification Team
Hello Bradley, Thank you for the report and test case. Verified as described. regards, Umesh
[19 Nov 2020 16:47]
Kevin Hoang
Hi, When will this bug be fixed? I'm getting the same issue when updating to MySql.Data version 8.0.22. Regards, Kevin
[27 Jan 2021 18:56]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL Connector/NET 8.0.24 release, and here's the proposed changelog entry from the documentation team: An exception was thrown if any CHAR(36) columns containing a NULL value were referenced in a query. New validation now checks for NULL values when the MySqlDbType member is Guid. Thank you for the bug report.
[9 Apr 2021 12:58]
MySQL Verification Team
Bug #103259 marked as duplicate of this one.
[8 Dec 2022 23:40]
Gustavo Amaya
The error persists despite having scaled the versions, from 8.0.24 to 31 to the present.