Can not get all columns when join table

[448700174]

select a.*, b.elder_name,b.insurance_no,b.gender,b.birth_day from medical_medicine_kit_order a, elder_info b where a.tenant_id = #{paramMap.tenantId} and a.elder_id = b.elder_id and a.status > 0

Logic SQL: select a.*, b.elder_name,b.insurance_no,b.gender,b.birth_day from medical_medicine_kit_order_12 a, elder_info b where a.elder_id = b.elder_id and a.status > 0 limit 10

Actual SQL: ds ::: select a.*, b.elder_name,b.insurance_no,b.gender,b.birth_day from medical_medicine_kit_order_12 a, elder_info b where a.elder_id = b.elder_id and a.status > 0 limit 10

Error attempting to get column 'id' from result set. Cause: java.sql.SQLFeatureNotSupportedException: Can not get index from column label id. ; Can not get index from column label id.; nested exception is java.sql.SQLFeatureNotSupportedException: Can not get index from column label id.

I can only get elder_name、insurance_no、gender、birth_day。

CREATE TABLE medical_medicine_kit_order ( id bigint unsigned NOT NULL COMMENT 'ID', elder_id int unsigned NOT NULL COMMENT ' ', tenant_id int unsigned NOT NULL COMMENT ' ', medicine_count tinyint NOT NULL COMMENT ' ', source tinyint NOT NULL COMMENT ''；）', type tinyint NOT NULL DEFAULT '1' COMMENT ' ', ... PRIMARY KEY (id) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci COMMENT='';

[strongduanmu]

Hi @448700174, can you try the latest version 5.4.1? I think this problem has been solved.

[448700174]

I have tried the 5.4.1, But it cannot execute correctly even a simple SQL.

And My configuration on 5.4.1 is as follows:

mode:
type: Standalone repository: type: JDBC props: sql-show: true databaseName: test dataSources: ds: dataSourceClassName: com.zaxxer.hikari.HikariDataSource driverClassName: com.mysql.cj.jdbc.Driver jdbcUrl: jdbc:mysql://xxx:3306/yb_test?allowMultiQueries=true&serverTimezone=GMT%2B8&characterEncoding=utf-8 username: xxx password: xxx minimumIdle: 2 idleTimeoutMilliseconds: 600000 maxPoolSize: 10 minPoolSize: 1 autoCommit: true poolName: MyHikariCP maxLifetimeMilliseconds: 1800000 connectionTimeout: 30000 connectionTestQuery: SELECT 1

rules:

• !SINGLE tables:
  • "."
• !SHARDING shardingAlgorithms: tenant_id_sharding: type: CLASS_BASED props: strategy: standard algorithmClassName: TenantIdShardingAlgorithm bindingTables:
  • medical_advice,medical_advice_main,medical_advice_group,medical_advice_item,medical_advice_dispense,medical_advice_settle,medical_advice_settle_item
  • medical_ward_schedule,medical_ward_record,medical_ward_abnormal
  • medical_medicine_kit_order,medical_medicine_kit_order_item
  • medical_chronic_follow,medical_chronic_data,medical_device_data,medical_device_alarm tables: medical_advice: actualDataNodes: ds.medicaladvice$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_advice_main: actualDataNodes: ds.medical_advice_main$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_advice_group: actualDataNodes: ds.medical_advice_group$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_advice_item: actualDataNodes: ds.medical_advice_item$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_advice_dispense: actualDataNodes: ds.medical_advice_dispense$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_advice_settle: actualDataNodes: ds.medical_advice_settle$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_advice_settle_item: actualDataNodes: ds.medical_advice_settle_item$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_ward_schedule: actualDataNodes: ds.medical_ward_schedule$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_ward_record: actualDataNodes: ds.medical_ward_record$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_ward_abnormal: actualDataNodes: ds.medical_ward_abnormal$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_medicine_kit_order: actualDataNodes: ds.medical_medicine_kit_order$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_medicine_kit_order_item: actualDataNodes: ds.medical_medicine_kit_order_item$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_chronic_follow: actualDataNodes: ds.medical_chronic_follow$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_chronic_data: actualDataNodes: ds.medical_chronic_data$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_device_data: actualDataNodes: ds.medical_device_data$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding medical_device_alarm: actualDataNodes: ds.medical_device_alarm$->{1..99} tableStrategy: standard: shardingColumn: tenant_id shardingAlgorithmName: tenant_id_sharding

[448700174]

Can you give me some suggestion on 5.4.1? I guess the problem is that I have not config the single tables with exact table name? But I don't want to do that because I have hundreds tables.

[github-actions[bot]]

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.