When querying multiple tables, the custom database and table sharding algorithm fails, but it takes effect when querying a single table.

[vwater]

<!-- 多数据源 -->
    <dependency>
        <groupId>com.baomidou</groupId>
        <artifactId>dynamic-datasource-spring-boot-starter</artifactId>
        <version>3.4.1</version>
    </dependency>

com.baomidou mybatis-plus-boot-starter 3.4.3.4

    <dependency>
        <groupId>org.apache.shardingsphere</groupId>
        <artifactId>shardingsphere-jdbc-core-spring-boot-starter</artifactId>
        <version>5.2.1</version>
        <exclusions>
            <exclusion>
                <artifactId>guava</artifactId>
                <groupId>com.google.guava</groupId>
            </exclusion>
            <exclusion>
                <artifactId>snakeyaml</artifactId>
                <groupId>org.yaml</groupId>
            </exclusion>
        </exclusions>
    </dependency>

[vwater]

Here is my demo, https://github.com/vwater/sharding-learn.git Execute unit test method testMultiQuery() I found that when sharding is combined with mybatisplus mybatisPlusTenantInterceptor, even if the code reaches the custom database sharding algorithm and custom table sharding algorithm, it will eventually perform a full database scan and a full table scan, causing the custom database sharding algorithm to fail.

[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.

[terrymanu]

shardingsphere-jdbc-core-spring-boot-starter is deprecated and removed in 5.3.0, please try new version and use ShardingSphere Driver.