zihaoAK47 opened a new issue, #30400:
URL: https://github.com/apache/shardingsphere/issues/30400

   ### Which version of ShardingSphere did you use?
   mysql version: 5.7.43
   master:  
[1a09be6c977fab34062340480620faf116a9645f](https://github.com/apache/shardingsphere/commit/1a09be6c977fab34062340480620faf116a9645f)
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-Proxy
   
   ### Expected behavior
   
![4](https://github.com/apache/shardingsphere/assets/106047330/e66aee3a-681b-4c69-b1a6-20df8286faed)
   
   ### Actual behavior
   
![1](https://github.com/apache/shardingsphere/assets/106047330/70eebf11-f2a0-40f5-b8fb-cfdbbbae64f5)
   
   ### Reason analyze (If you can)
   Hi community, when configuring all query statements to be executed using the 
federated engine, the following error message will appear when the MySQL SQL 
statement projection column result is of boolean type:
   
![1](https://github.com/apache/shardingsphere/assets/106047330/70eebf11-f2a0-40f5-b8fb-cfdbbbae64f5)
   
   I couldn't find a definition for the boolean type, but based on the query 
results, MySQL uses 0 and 1 to represent the boolean:
   
![2](https://github.com/apache/shardingsphere/assets/106047330/28d501fb-ab1f-4143-b364-34b35020aa6f)
   
   I will match the jdbcType boolean with TINY and get the following error 
message. There was no error during proxy execution, but there will be no result 
display:
   
![3](https://github.com/apache/shardingsphere/assets/106047330/9ffc8fb5-d8d2-4fd4-bd0c-5c85b89d9011)
   
   I received the following error message during testing on e2e:
   
![5](https://github.com/apache/shardingsphere/assets/106047330/49cf825b-0f81-4692-9d98-3632a5d56606)
   
![6](https://github.com/apache/shardingsphere/assets/106047330/5156194b-67dd-4dfc-9ce2-1a24eb4b2606)
   
   
   The metadata obtained during the calcite execution phase and the execution 
result are true, false, rather than the 1 or 0 corresponding to MySQL
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   You can refer to the configuration here to reproduce the problem: #28895
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to