Bug #97486 | mysql8.0 If the select SQL query statement is too long, the bit result will be w | ||
---|---|---|---|
Submitted: | 5 Nov 2019 3:53 | Modified: | 6 Nov 2019 15:08 |
Reporter: | wuzhenxing wu | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
Version: | 8.0.17 | OS: | Windows (10) |
Assigned to: | CPU Architecture: | x86 (x64) | |
Tags: | MySQL |
[5 Nov 2019 3:53]
wuzhenxing wu
[5 Nov 2019 13:32]
MySQL Verification Team
Hi Mr. wu, Thank you for your bug report. In order to proceed , we need further info from you. Please, show us with column types of the result set, how and why is a type of the field wrong. Show us the correct and wrong types returned. Next, let us know which release of 8.0 do you use ??? After we get these results, we shall proceed with other questions ......
[5 Nov 2019 13:41]
MySQL Verification Team
Turns out that this bug is a duplicate of: https://bugs.mysql.com/bug.php?id=97113
[5 Nov 2019 15:10]
wuzhenxing wu
-- MySQL dump 10.13 Distrib 8.0.17, for Win64 (x86_64) -- -- Host: localhost Database: qkjl -- ------------------------------------------------------ -- Server version 8.0.17 /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!50503 SET NAMES utf8 */; /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; -- -- Table structure for table `t_admin` -- DROP TABLE IF EXISTS `t_admin`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!50503 SET character_set_client = utf8mb4 */; CREATE TABLE `t_admin` ( `super_privilege` bit(1) NOT NULL, `id` varchar(36) NOT NULL, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `t_admin` -- LOCK TABLES `t_admin` WRITE; /*!40000 ALTER TABLE `t_admin` DISABLE KEYS */; INSERT INTO `t_admin` VALUES (_binary '','6f0fecea-4faf-42a7-9272-bf8a2988faa1'),(_binary '\0','6f0fecea-4faf-42a7-9272-bf8a2988faae'); /*!40000 ALTER TABLE `t_admin` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `t_user` -- DROP TABLE IF EXISTS `t_user`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!50503 SET character_set_client = utf8mb4 */; CREATE TABLE `t_user` ( `id` varchar(36) NOT NULL, `create_gmt` datetime DEFAULT NULL, `avatar` varchar(255) DEFAULT NULL, `last_login_date` datetime DEFAULT NULL, `nickname` varchar(255) DEFAULT NULL, `password` varchar(255) DEFAULT NULL, `username` varchar(255) DEFAULT NULL, `wx_key` varchar(255) DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `t_user` -- LOCK TABLES `t_user` WRITE; /*!40000 ALTER TABLE `t_user` DISABLE KEYS */; INSERT INTO `t_user` VALUES ('6f0fecea-4faf-42a7-9272-bf8a2988faae','2019-09-25 11:54:42','089a4f6d96e94c6dab7e8ea908f76597',NULL,'野猪配钥匙',NULL,NULL,'xx'),('6f0fecea-4faf-42a7-9272-bf8a2988faa1','2019-11-05 21:15:12',NULL,'2019-11-05 21:15:59','hellowo','1','1',NULL); /*!40000 ALTER TABLE `t_user` ENABLE KEYS */; UNLOCK TABLES; /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; -- Dump completed on 2019-11-05 23:09:13 Try the SQL above
[5 Nov 2019 16:47]
MySQL Verification Team
Thank you Mr. wu, I have tested your SQL and it confirmed that your report is a duplicate of the already verified bug ...
[6 Nov 2019 15:08]
wuzhenxing wu
thank u Is there a solution?
[6 Nov 2019 15:37]
MySQL Verification Team
Verified bugs are scheduled for fixing by a special internal team, in such a way that we do not have access to the results of when is fix planned for. Regarding workaround, try any of the casting options, as described in our Reference Manual.