I've written a reproducer, attached. Behaviour changes between 8.0.27-0ubuntu0.21.10.1 and 8.0.28-0ubuntu3. Before, running "SELECT ? AS a" as a parameterized query, supplying a MYSQL_TYPE_DATETIME using the MYSQL_TIME struct, then the result was a single row with one field with a MYSQL_TYPE_DATETIME object. After, the same thing results in a different type (I think a string). This is causing the ruby-mysql2 dep8 failure, because it assumes that a MYSQL_TYPE_DATETIME is returned in this case.
The MySQL 8.0.28 release notes discuss some changes to the way that types are interpreted: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-28.html However it's not clear to me that this behaviour change is intentional, and it seems reasonable to me that given the input type is known in this case, the output type should be the same. So it does seem like a MySQL upstream regression to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961617 Title: String returned when DATETIME expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1961617/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
