Loading sharding-jdbc-core/src/test/resources/yaml/config/config-all.yaml +1 −5 Original line number Diff line number Diff line Loading @@ -14,13 +14,11 @@ dataSources: shardingRule: defaultDataSourceName: db0 defaultKeyGeneratorClass: io.shardingjdbc.core.yaml.fixture.IncrementKeyGenerator tables: config: actualDataNodes: db${0..1}.config_${0..1} t_order: actualDataNodes: db${0..1}.t_order_${0..1} databaseStrategy: Loading @@ -35,7 +33,6 @@ shardingRule: actualDataNodes: db${0..1}.t_order_item_${0..1} keyGeneratorColumnName: order_item_id keyGeneratorClass: io.shardingjdbc.core.yaml.fixture.DecrementKeyGenerator #绑定表中其余的表的策略与第一张表的策略相同 databaseStrategy: standard: shardingColumn: order_id Loading @@ -48,7 +45,6 @@ shardingRule: bindingTables: - t_order,t_order_item #默认数据库分片策略 defaultDatabaseStrategy: complex: shardingColumns: order_id, user_id Loading sharding-jdbc-core/src/test/resources/yaml/config/config-bindingError.yaml +0 −1 Original line number Diff line number Diff line Loading @@ -12,7 +12,6 @@ shardingRule: algorithmExpression: t_order_${id % 2} t_order_item: actualDataNodes: ds.t_order_item_${0..1} #绑定表中其余的表的策略与第一张表的策略相同 databaseStrategy: standard: shardingColumn: order_id Loading sharding-jdbc-core/src/test/resources/yaml/integrate/ms/configWithMasterSlaveDataSourceWithoutProps.yaml +0 −2 Original line number Diff line number Diff line Loading @@ -20,9 +20,7 @@ dataSources: masterSlaveRule: name: db_ms masterDataSourceName: db_master slaveDataSourceNames: [db_slave_0, db_slave_1] configMap: key1: value1 sharding-jdbc-core/src/test/resources/yaml/integrate/sharding/configWithDataSourceWithProps.yaml +0 −4 Original line number Diff line number Diff line Loading @@ -16,7 +16,6 @@ shardingRule: tables: config: actualDataNodes: db${0..1}.t_config t_order: actualDataNodes: db${0..1}.t_order_${0..1} databaseStrategy: Loading @@ -29,10 +28,8 @@ shardingRule: algorithmExpression: t_order_${order_id % 2} keyGeneratorColumnName: order_id keyGeneratorClass: io.shardingjdbc.core.yaml.fixture.IncrementKeyGenerator t_order_item: actualDataNodes: db${0..1}.t_order_item_${0..1} #绑定表中其余的表的策略与第一张表的策略相同 databaseStrategy: standard: shardingColumn: user_id Loading @@ -45,7 +42,6 @@ shardingRule: bindingTables: - t_order,t_order_item #默认数据库分片策略 defaultDatabaseStrategy: none: defaultTableStrategy: Loading sharding-jdbc-core/src/test/resources/yaml/integrate/sharding/configWithDataSourceWithoutProps.yaml +0 −4 Original line number Diff line number Diff line Loading @@ -16,7 +16,6 @@ shardingRule: tables: config: actualDataNodes: db${0..1}.t_config t_order: actualDataNodes: db${0..1}.t_order_${0..1} databaseStrategy: Loading @@ -29,10 +28,8 @@ shardingRule: algorithmExpression: t_order_${order_id % 2} keyGeneratorColumnName: order_id keyGeneratorClass: io.shardingjdbc.core.yaml.fixture.IncrementKeyGenerator t_order_item: actualDataNodes: db${0..1}.t_order_item_${0..1} #绑定表中其余的表的策略与第一张表的策略相同 databaseStrategy: standard: shardingColumn: user_id Loading @@ -44,7 +41,6 @@ shardingRule: bindingTables: - t_order,t_order_item #默认数据库分片策略 defaultDatabaseStrategy: none: defaultTableStrategy: Loading Loading
sharding-jdbc-core/src/test/resources/yaml/config/config-all.yaml +1 −5 Original line number Diff line number Diff line Loading @@ -14,13 +14,11 @@ dataSources: shardingRule: defaultDataSourceName: db0 defaultKeyGeneratorClass: io.shardingjdbc.core.yaml.fixture.IncrementKeyGenerator tables: config: actualDataNodes: db${0..1}.config_${0..1} t_order: actualDataNodes: db${0..1}.t_order_${0..1} databaseStrategy: Loading @@ -35,7 +33,6 @@ shardingRule: actualDataNodes: db${0..1}.t_order_item_${0..1} keyGeneratorColumnName: order_item_id keyGeneratorClass: io.shardingjdbc.core.yaml.fixture.DecrementKeyGenerator #绑定表中其余的表的策略与第一张表的策略相同 databaseStrategy: standard: shardingColumn: order_id Loading @@ -48,7 +45,6 @@ shardingRule: bindingTables: - t_order,t_order_item #默认数据库分片策略 defaultDatabaseStrategy: complex: shardingColumns: order_id, user_id Loading
sharding-jdbc-core/src/test/resources/yaml/config/config-bindingError.yaml +0 −1 Original line number Diff line number Diff line Loading @@ -12,7 +12,6 @@ shardingRule: algorithmExpression: t_order_${id % 2} t_order_item: actualDataNodes: ds.t_order_item_${0..1} #绑定表中其余的表的策略与第一张表的策略相同 databaseStrategy: standard: shardingColumn: order_id Loading
sharding-jdbc-core/src/test/resources/yaml/integrate/ms/configWithMasterSlaveDataSourceWithoutProps.yaml +0 −2 Original line number Diff line number Diff line Loading @@ -20,9 +20,7 @@ dataSources: masterSlaveRule: name: db_ms masterDataSourceName: db_master slaveDataSourceNames: [db_slave_0, db_slave_1] configMap: key1: value1
sharding-jdbc-core/src/test/resources/yaml/integrate/sharding/configWithDataSourceWithProps.yaml +0 −4 Original line number Diff line number Diff line Loading @@ -16,7 +16,6 @@ shardingRule: tables: config: actualDataNodes: db${0..1}.t_config t_order: actualDataNodes: db${0..1}.t_order_${0..1} databaseStrategy: Loading @@ -29,10 +28,8 @@ shardingRule: algorithmExpression: t_order_${order_id % 2} keyGeneratorColumnName: order_id keyGeneratorClass: io.shardingjdbc.core.yaml.fixture.IncrementKeyGenerator t_order_item: actualDataNodes: db${0..1}.t_order_item_${0..1} #绑定表中其余的表的策略与第一张表的策略相同 databaseStrategy: standard: shardingColumn: user_id Loading @@ -45,7 +42,6 @@ shardingRule: bindingTables: - t_order,t_order_item #默认数据库分片策略 defaultDatabaseStrategy: none: defaultTableStrategy: Loading
sharding-jdbc-core/src/test/resources/yaml/integrate/sharding/configWithDataSourceWithoutProps.yaml +0 −4 Original line number Diff line number Diff line Loading @@ -16,7 +16,6 @@ shardingRule: tables: config: actualDataNodes: db${0..1}.t_config t_order: actualDataNodes: db${0..1}.t_order_${0..1} databaseStrategy: Loading @@ -29,10 +28,8 @@ shardingRule: algorithmExpression: t_order_${order_id % 2} keyGeneratorColumnName: order_id keyGeneratorClass: io.shardingjdbc.core.yaml.fixture.IncrementKeyGenerator t_order_item: actualDataNodes: db${0..1}.t_order_item_${0..1} #绑定表中其余的表的策略与第一张表的策略相同 databaseStrategy: standard: shardingColumn: user_id Loading @@ -44,7 +41,6 @@ shardingRule: bindingTables: - t_order,t_order_item #默认数据库分片策略 defaultDatabaseStrategy: none: defaultTableStrategy: Loading