Ⅰ. Issue Description
similar table names cause "Not support the table has the same column name with different case yet".
such as:bill_test、bill_test_data_0.
Ⅱ. Describe what happened
io.seata.rm.datasource.sql.struct.cache.MysqlTableMetaCache#resultSetMetaToSchema
line 117:ResultSet rsColumns = dbmd.getColumns(catalogName, schemaName, tableName, "%")
Caused by: io.seata.common.exception.NotSupportYetException: Not support the table has the same column name with different case yet
at io.seata.rm.datasource.sql.struct.cache.MysqlTableMetaCache.resultSetMetaToSchema(MysqlTableMetaCache.java:142) ~[seata-all-1.5.2.jar:1.5.2]
at io.seata.rm.datasource.sql.struct.cache.MysqlTableMetaCache.fetchSchema(MysqlTableMetaCache.java:83) ~[seata-all-1.5.2.jar:1.5.2]
... 147 common frames omitted
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Ⅴ. Anything else we need to know?
Ⅵ. Environment:
- JDK 1.8
- Seata server 1.7.0
- Seata client 1.5.2
- MySQL 5.7
- shardingsphere-jdbc-core 5.3.1
- shardingsphere-transaction-base-seata-at 5.3.1
- mysql-connector-java 8.0.21
3条答案
按热度按时间35g0bw711#
Please check if your column name exists with just a difference in uppercase and lowercase.
8fsztsew2#
You can paste the table structure here by executing show create table.
cyvaqqii3#
You can paste the table structure here by executing show create table.
ShardingSphere-JDBC may have configuration problems. We formatted the configuration rules ourselves and finally loaded them by ShardingSphere-JDBC
just delete the next part and it'll work
if there is a configuration, mysql-connector-java:8.0.21 will find two tables
seata-all:1.5.2 atches the id of bill_storage_data_0 with the data of bill_storage once