You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2022/12/29 07:56:37 UTC
[GitHub] [shardingsphere] TeslaCN opened a new issue, #23159: Wrong unsigned flag was persist to cluster persist repository
TeslaCN opened a new issue, #23159:
URL: https://github.com/apache/shardingsphere/issues/23159
## Bug Report
### Which version of ShardingSphere did you use?
master - 39b29c120773b8d9ae60a52d720707c3733b99ff
https://github.com/apache/shardingsphere/pull/21960
This may impact ShardingSphere 5.3.0.
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
### Expected behavior
Columns of t_data_type_integer_unsigned should be unsigned.
### Actual behavior
--
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: notifications-unsubscribe@shardingsphere.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] tristaZero closed issue #23159: Wrong unsigned flag was persist to cluster persist repository
Posted by GitBox <gi...@apache.org>.
tristaZero closed issue #23159: Wrong unsigned flag was persist to cluster persist repository
URL: https://github.com/apache/shardingsphere/issues/23159
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org