Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
A community reported protocol regression error against MySQL - https://github.com/launchbadge/sqlx/issues/1664, resulted in upstream bug - https://bugs.mysql.com/bug.php?id=106352. A user comment pointed out that MariaDB-10.7 has this error.
Essentially SELECT ? wasn't returning the datatype in binary protocol when the arg was cast as a DATETIME or DATE or TIME type.
MySQL fix Bug#33813951, Change-Id: I2448e3f2f36925fe70d882ae5681a6234f0d5a98.
Cherry-picking the test commit.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| issue.field.resolutiondate | 2023-09-08 08:23:38.0 | 2023-09-08 08:23:38.194 |
| Fix Version/s | 10.4.32 [ 29300 ] | |
| Fix Version/s | 10.5.23 [ 29012 ] | |
| Fix Version/s | 10.6.16 [ 29014 ] | |
| Fix Version/s | 10.10.7 [ 29018 ] | |
| Fix Version/s | 10.11.6 [ 29020 ] | |
| Fix Version/s | 11.0.4 [ 29021 ] | |
| Fix Version/s | 11.1.3 [ 29023 ] | |
| Fix Version/s | 11.2.2 [ 29035 ] | |
| Fix Version/s | 10.4 [ 22408 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
Contrary to the users statement, we didn't have a problem.
But we ported the test case to make sure we never do.
Thanks bar for the analysis, finding and porting the MySQL test case.