Wrong LIMIT rewrite while GROUP BY and ORDER BY on different items #2062

joooohnli · 2019-03-20T05:43:48Z

Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

Searched open and closed GitHub issues.
Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details.
If no response more than 7 days and we cannot reproduce it on current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Which version of ShardingSphere did you use?

3.1.0

Which project did you use? Sharding-JDBC or Sharding-Proxy?

Sharding-JDBC

Expected behavior

limit 0, 10

Actual behavior

 SQL: select max(sid) as sid, max(sendTime) as sendTime, objectId, sum(0) as unreadCount from TEST where memberId = ? and status != -1 group by objectId order by sendTime desc limit ?, ?
SQL-BindValue: 52146792, 0, 2147483647

Reason analyze (If you can)

logic error：

io.shardingsphere.core.routing.router.sharding.ParsingSQLRouter#processLimit

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

Run it with PreparedStatement:

select max(sid) as sid, max(sendTime) as sendTime, objectId, sum(0) as unreadCount from TEST where memberId = ? and status != -1 group by objectId order by sendTime desc limit ?, ?

Example codes for reproduce this issue (such as a github link).

The text was updated successfully, but these errors were encountered:

tuohai666 · 2019-03-20T08:22:03Z

@joooohnli Please try to describe the "Expected behavior" and "Actual behavior" clearly. I'm not saying you must use many words. Think about it very carefully before you responsd, thanks.

joooohnli · 2019-03-21T03:24:14Z

@tuohai666

Expected behavior

What I input is limit 0, 10

Actual behavior

What I really got is limit 0, 2147483647 you can see as below:

SQL: select max(sid) as sid, max(sendTime) as sendTime, objectId, sum(0) as unreadCount from TEST where memberId = ? and status != -1 group by objectId order by sendTime desc limit ?, ?
SQL-BindValue: 52146792, 0, 2147483647

tuohai666 · 2019-03-21T03:49:59Z

I am not very sure what's the problem. I don't know where the log come from. So I must know the behavior.
Let me guess what the program behavior you haven seen:

You input a sql and expect a result with 10 rows. If you don't use Sharding-JDBC, you connect to mysql directly, execute the same sql, you got 10 rows. That means your expect is right.
But you got and saw 2147483647 rows in your screen.

Please answer are the two above right? If they are right, please prove you got 2147483647 rows, you don't need to past all 2147483647, but try to prove it. Don't use log to prove it, I think the log is not from Sharding-JDBC.

Also, please provide the example codes and configurations.

BTW, What I input is limit 0, 10 is your behavior, it's not the program behavior.

joooohnli · 2019-03-21T06:56:15Z

@tuohai666
Here is the example code

            connection = dataSource.getConnection();
            PreparedStatement preparedStatement = connection.prepareStatement("select max(sid) as sid, max(sendTime) as sendTime, objectId, sum(0) as unreadCount from TEST where memberId = ? and status != -1 group by objectId order by sendTime desc limit ?, ?");
            preparedStatement.setInt(1, 123);
            preparedStatement.setInt(2, 0);
            preparedStatement.setInt(3, 10);
            ResultSet resultSet = preparedStatement.executeQuery();

And TEST is just a single table in defaultDataSource. (in fact this issue also occurs to sharding table)

The log comes from my jdbc monitor, it shows the real sql that jdbc sends to physical db.

If you think the log is not convincing. I can show you the debug info:
io.shardingsphere.core.parsing.parser.context.limit.Limit#rewrite

Actually you could have reproduced this bug according to the Steps to reproduce the behavior.

tuohai666 · 2019-03-21T07:27:46Z

Set sql.show : true to get a Sharding-JDBC log.
I have got your monitor log and understand very clearly, but we talk only Sharding-JDBC log from now on. Don't put your debug info here, thanks.
Your monitor log is never a behavior of Sharding-JDBC. To describe a behavior show the result rows please. I will not ask you to put 2147483647 rows here, you can only put 11 rows to prove there is a bug.
I can't reproduce it because I don't have the configuration, I even don't know what's in your database.
Focus on the result rows. It's not helpful to analyze before you find out what you want and what you acutally get.
More detail. Please answer these two questions:
Access MySQL Server without Sharding-JDBC: how many rows will return when you execute this SQL?
Access MySQL Server with Sharding-JDBC: how many rows will return when you execute this SQL?
And put the results here.

joooohnli · 2019-03-21T08:48:18Z

2019-03-21 14:57:16.416  INFO 70268 --- [nio-8090-exec-1] ShardingSphere-SQL                       : Rule Type: sharding
2019-03-21 14:57:16.416  INFO 70268 --- [nio-8090-exec-1] ShardingSphere-SQL                       : Logic SQL: select max(sid) as sid, max(sendTime) as sendTime, objectId, sum(0) as unreadCount from TEST where memberId = ? and status != -1 group by objectId order by sendTime desc limit ?, ?
2019-03-21 14:57:16.416  INFO 70268 --- [nio-8090-exec-1] ShardingSphere-SQL                       : SQLStatement: SelectStatement(super=DQLStatement(super=io.shardingsphere.core.parsing.parser.sql.dql.select.SelectStatement@4db4cf4f), containStar=false, firstSelectItemStartPosition=7, selectListLastPosition=83, groupByLastPosition=153, items=[AggregationSelectItem(type=MAX, innerExpression=(sid), alias=Optional.of(sid), derivedAggregationSelectItems=[], index=-1), AggregationSelectItem(type=MAX, innerExpression=(sendTime), alias=Optional.of(sendTime), derivedAggregationSelectItems=[], index=-1), CommonSelectItem(expression=objectId, alias=Optional.absent()), AggregationSelectItem(type=SUM, innerExpression=(0), alias=Optional.of(unreadCount), derivedAggregationSelectItems=[], index=-1)], groupByItems=[OrderItem(owner=Optional.absent(), name=Optional.of(objectId), orderDirection=ASC, nullOrderDirection=ASC, index=-1, expression=null, alias=Optional.absent())], orderByItems=[OrderItem(owner=Optional.absent(), name=Optional.of(sendTime), orderDirection=DESC, nullOrderDirection=ASC, index=-1, expression=null, alias=Optional.of(sendTime))], limit=Limit(offset=LimitValue(value=0, index=1, boundOpened=false), rowCount=LimitValue(value=10, index=2, boundOpened=false)), subQueryStatement=null, subQueryStatements=[], subQueryConditions=[])
2019-03-21 14:57:16.416  INFO 70268 --- [nio-8090-exec-1] ShardingSphere-SQL                       : Actual SQL: test ::: select max(sid) as sid, max(sendTime) as sendTime, objectId, sum(0) as unreadCount from TEST where memberId = ? and status != -1 group by objectId order by sendTime desc limit ?, ? ::: [[123, 0, 2147483647]]

Sharding log as ablove.
Are you sure the debug info does not help. Do you think rewriting limit count to 2147483647 is reseassonable in this case?
ok
There is nothing about my database. Sharding-jdbc rewrites the sql, it happens before the sql being sent to the database.
I am much clear what I want and what I get, which was represented in the issue report.
a. 10 rows; b. more than 10 rows

This issue happened on my prod environment and leaded to some horrible consequences. I could 100% reproduce it. There is no special precondition. You can also reproduce it according to the Steps to reproduce the behavior. Just try it.

tuohai666 · 2019-03-21T09:35:04Z

Thanks for your effort. This is the exactly information I wanted.
I'll find out whether this problem is a known issue.
If it is a new bug, it will be fixed in release 4.0.0-RC2.

#2062, fix SQL rewrite issue (#2086)

#2062, Wrong LIMIT rewrite while GROUP BY and ORDER BY on different items

tuohai666 · 2019-03-26T10:17:03Z

@joooohnli Resolved. Thanks for your report. You can try with dev branch now. This modification will be included in 4.0.0-RC1 which will be released this week.

Anricx · 2019-04-05T14:03:17Z

so, will there be no hotfix for 3.x? @terrymanu

lyflyy · 2021-06-14T09:06:37Z

I also had this issue in 【4.1.1】

Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

Searched open and closed GitHub issues.
Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Which version of ShardingSphere did you use?

4.1.1

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-JDBC

Expected behavior

I want to return 10 pieces of data in the SQL result

Actual behavior

The rewritten SQL queries 2147483647 pieces of data

Reason analyze (If you can)

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

ShardingSphere-SQL LOG detail

2021-06-14 16:40:46.205 DEBUG 12448 --- [nio-8080-exec-1] c.s.d.mapper.OrdersMapper.officialDemo   : ==>  Preparing: SELECT user_id, SUM(price) `sum` FROM orders where create_time > ? and create_time < ? GROUP BY user_id ORDER BY `sum` DESC LIMIT 0, 10 
2021-06-14 16:40:46.231 DEBUG 12448 --- [nio-8080-exec-1] c.s.d.mapper.OrdersMapper.officialDemo   : ==> Parameters: 2020-07-09 13:54:57.0(Timestamp), 2022-07-19 13:54:57.0(Timestamp)
2021-06-14 16:40:47.088  INFO 12448 --- [nio-8080-exec-1] ShardingSphere-SQL                       : Logic SQL: SELECT user_id, SUM(price) `sum` FROM orders
         
            where create_time > ? and create_time < ?
         
        GROUP BY user_id ORDER BY `sum` DESC LIMIT 0, 10
2021-06-14 16:40:47.088  INFO 12448 --- [nio-8080-exec-1] ShardingSphere-SQL                       : SQLStatement: SelectStatementContext(super=CommonSQLStatementContext(sqlStatement=org.apache.shardingsphere.sql.parser.sql.statement.dml.SelectStatement@109c4794, tablesContext=org.apache.shardingsphere.sql.parser.binder.segment.table.TablesContext@66e38b62), tablesContext=org.apache.shardingsphere.sql.parser.binder.segment.table.TablesContext@66e38b62, projectionsContext=ProjectionsContext(startIndex=7, stopIndex=31, distinctRow=false, projections=[ColumnProjection(owner=null, name=user_id, alias=Optional.empty), AggregationProjection(type=SUM, innerExpression=(price), alias=Optional[sum], derivedAggregationProjections=[], index=-1)]), groupByContext=org.apache.shardingsphere.sql.parser.binder.segment.select.groupby.GroupByContext@1bba7f5d, orderByContext=org.apache.shardingsphere.sql.parser.binder.segment.select.orderby.OrderByContext@3e02c417, paginationContext=org.apache.shardingsphere.sql.parser.binder.segment.select.pagination.PaginationContext@4c5084a4, containsSubquery=false)
2021-06-14 16:40:47.088  INFO 12448 --- [nio-8080-exec-1] ShardingSphere-SQL                       : Actual SQL: dbs0 ::: SELECT user_id, SUM(price) `sum` FROM orders_6
         
            where create_time > ? and create_time < ?
         
        GROUP BY user_id ORDER BY `sum` DESC LIMIT 0, 2147483647 ::: [2020-07-09 13:54:57.0, 2022-07-19 13:54:57.0]
2021-06-14 16:40:47.088  INFO 12448 --- [nio-8080-exec-1] ShardingSphere-SQL                       : Actual SQL: dbs1 ::: SELECT user_id, SUM(price) `sum` FROM orders_6
         
            where create_time > ? and create_time < ?
         
        GROUP BY user_id ORDER BY `sum` DESC LIMIT 0, 2147483647 ::: [2020-07-09 13:54:57.0, 2022-07-19 13:54:57.0]
2021-06-14 16:40:47.088  INFO 12448 --- [nio-8080-exec-1] ShardingSphere-SQL                       : Actual SQL: dbs2 ::: SELECT user_id, SUM(price) `sum` FROM orders_6
         
            where create_time > ? and create_time < ?
         
        GROUP BY user_id ORDER BY `sum` DESC LIMIT 0, 2147483647 ::: [2020-07-09 13:54:57.0, 2022-07-19 13:54:57.0]
2021-06-14 16:40:48.780 DEBUG 12448 --- [nio-8080-exec-1] c.s.d.mapper.OrdersMapper.officialDemo   : <==      Total: 10

Example codes for reproduce this issue (such as a github link).

I use read/write separation and my configuration file is as follows

# 数据源 db0,db1
logging.level.com.sharding.demo.mapper=debug

spring.shardingsphere.props.sql.show=true
spring.shardingsphere.props.max.connections.size.per.query=1

mybatis-plus.mapper-locations=classpath:/mapper/*.xml

spring.shardingsphere.datasource.names = db0,db1,db2,dbs0,dbs1,dbs2

spring.shardingsphere.datasource.db0.type = com.zaxxer.hikari.HikariDataSource
spring.shardingsphere.datasource.db0.driver-class-name = com.mysql.cj.jdbc.Driver
spring.shardingsphere.datasource.db0.jdbc-url = jdbc:mysql://127.0.0.1:3306/db0?characterEncoding=utf8&useSSL=false
spring.shardingsphere.datasource.db0.username = root
spring.shardingsphere.datasource.db0.password = root

spring.shardingsphere.datasource.db1.type = com.zaxxer.hikari.HikariDataSource
spring.shardingsphere.datasource.db1.driver-class-name = com.mysql.cj.jdbc.Driver
spring.shardingsphere.datasource.db1.jdbc-url = jdbc:mysql://127.0.0.1:3306/db1?characterEncoding=utf8&useSSL=false
spring.shardingsphere.datasource.db1.username = root
spring.shardingsphere.datasource.db1.password = root

spring.shardingsphere.datasource.db2.type = com.zaxxer.hikari.HikariDataSource
spring.shardingsphere.datasource.db2.driver-class-name = com.mysql.cj.jdbc.Driver
spring.shardingsphere.datasource.db2.jdbc-url = jdbc:mysql://127.0.0.1:3306/db2?characterEncoding=utf8&useSSL=false
spring.shardingsphere.datasource.db2.username = root
spring.shardingsphere.datasource.db2.password = root

spring.shardingsphere.datasource.dbs0.type = com.zaxxer.hikari.HikariDataSource
spring.shardingsphere.datasource.dbs0.driver-class-name = com.mysql.cj.jdbc.Driver
spring.shardingsphere.datasource.dbs0.jdbc-url = jdbc:mysql://127.0.0.1:3307/db0?characterEncoding=utf8&useSSL=false
spring.shardingsphere.datasource.dbs0.username = root
spring.shardingsphere.datasource.dbs0.password = root

spring.shardingsphere.datasource.dbs1.type = com.zaxxer.hikari.HikariDataSource
spring.shardingsphere.datasource.dbs1.driver-class-name = com.mysql.cj.jdbc.Driver
spring.shardingsphere.datasource.dbs1.jdbc-url = jdbc:mysql://127.0.0.1:3307/db1?characterEncoding=utf8&useSSL=false
spring.shardingsphere.datasource.dbs1.username = root
spring.shardingsphere.datasource.dbs1.password = root

spring.shardingsphere.datasource.dbs2.type = com.zaxxer.hikari.HikariDataSource
spring.shardingsphere.datasource.dbs2.driver-class-name = com.mysql.cj.jdbc.Driver
spring.shardingsphere.datasource.dbs2.jdbc-url = jdbc:mysql://127.0.0.1:3307/db2?characterEncoding=utf8&useSSL=false
spring.shardingsphere.datasource.dbs2.username = root
spring.shardingsphere.datasource.dbs2.password = root

#master-slave   基于master1和master2主从集群实现读写分离
spring.shardingsphere.sharding.master-slave-rules.db0.master-data-source-name=db0
spring.shardingsphere.sharding.master-slave-rules.db0.slave-data-source-names=dbs0

spring.shardingsphere.sharding.master-slave-rules.db1.master-data-source-name=db1
spring.shardingsphere.sharding.master-slave-rules.db1.slave-data-source-names=dbs1

spring.shardingsphere.sharding.master-slave-rules.db2.master-data-source-name=db2
spring.shardingsphere.sharding.master-slave-rules.db2.slave-data-source-names=dbs2

#多个从库的时候使用负载均衡
spring.shardingsphere.masterslave.load-balance-algorithm-type=ROUND_ROBIN

# user 表策略 用户按照性别进行分库， 2个库, id取模进行分表 3张表, db_male ,db_female user_0, user_1, user_2
# 分库策略 根据id取模确定数据进哪个数据库
spring.shardingsphere.sharding.tables.user.database-strategy.inline.sharding-column = sex
spring.shardingsphere.sharding.tables.user.database-strategy.inline.algorithm-expression = db$->{sex % 2}
# 分表策略
spring.shardingsphere.sharding.tables.user.actual-data-nodes = db$->{0..1}.user_$->{0..2}
# 分表字段member_id
spring.shardingsphere.sharding.tables.user.table-strategy.inline.sharding-column = id
# 分表策略 根据member_id取模,确定数据最终落在那个表中
spring.shardingsphere.sharding.tables.user.table-strategy.inline.algorithm-expression = user_$->{id % 3}
# 使用SNOWFLAKE算法生成主键
spring.shardingsphere.sharding.tables.user.key-generator.column = id
spring.shardingsphere.sharding.tables.user.key-generator.type = SNOWFLAKE


# 商品按照类型取模分库，3个库，id取模进行分表 db_type1, db_type2, db_type3, goods_0, goods_1, goods_2
# 分库策略 根据id取模确定数据进哪个数据库
spring.shardingsphere.sharding.tables.goods.database-strategy.inline.sharding-column = type
spring.shardingsphere.sharding.tables.goods.database-strategy.inline.algorithm-expression = db$->{type % 3}
# 分表策略
spring.shardingsphere.sharding.tables.goods.actual-data-nodes = db$->{0..2}.goods_$->{0..2}
# 分表字段member_id
spring.shardingsphere.sharding.tables.goods.table-strategy.inline.sharding-column = id
# 分表策略 根据member_id取模,确定数据最终落在那个表中
spring.shardingsphere.sharding.tables.goods.table-strategy.inline.algorithm-expression = goods_$->{id % 3}
# 使用SNOWFLAKE算法生成主键
spring.shardingsphere.sharding.tables.goods.key-generator.column = id
spring.shardingsphere.sharding.tables.goods.key-generator.type = SNOWFLAKE


# 订单按照下单月份进行分表，年份进行分库， db_2020,db_2021,db_2022
#声明虚拟表
spring.shardingsphere.sharding.tables.orders.actual-data-nodes=db$->{0..2}.orders_$->{0..11}
#声明表内的主键
spring.shardingsphere.sharding.tables.orders.key-generator.column=id
#声明主键生成策略
spring.shardingsphere.sharding.tables.orders.key-generator.type=SNOWFLAKE
##声明根据哪个字段进行分片
spring.shardingsphere.sharding.tables.orders.database-strategy.standard.sharding-column=create_time
##自定义分片规则类
## 分库规则orders_auto_increment
spring.shardingsphere.sharding.tables.orders.database-strategy.standard.precise-algorithm-class-name=com.sharding.demo.algorithm.OrderDatabaseShardingAlgorithm
spring.shardingsphere.sharding.tables.orders.database-strategy.standard.range-algorithm-class-name=com.sharding.demo.algorithm.OrderDatabaseShardingRangeAlgorithm
#声明根据哪个字段进行分片
spring.shardingsphere.sharding.tables.orders.table-strategy.standard.sharding-column=create_time
#自定义分片规则类
spring.shardingsphere.sharding.tables.orders.table-strategy.standard.precise-algorithm-class-name=com.sharding.demo.algorithm.OrderTableShardingAlgorithm
spring.shardingsphere.sharding.tables.orders.table-strategy.standard.range-algorithm-class-name=com.sharding.demo.algorithm.OrderTableShardingRangeAlgorithm

# 配置公共表
# 一个实体类对应两张表，覆盖
spring.main.allow-bean-definition-overriding=true
spring.shardingsphere.sharding.broadcast-tables=common_dict
# 配置数据库中 t_dict 表主键 dict_id 生成策略 SNOWFLAKE 雪花算法
spring.shardingsphere.sharding.tables.common_dict.key-generator.column=dict_id
spring.shardingsphere.sharding.tables.common_dict.key-generator.type=SNOWFLAKE

i use mybatis

<select id="officialDemo" resultType="com.sharding.demo.vo.OffocialDemoVo">
    SELECT user_id, SUM(price) `sum` FROM orders
    <if test="orders.createTimeStart != null">
        where create_time > #{orders.createTimeStart} and create_time &lt; #{orders.createTimeEnd}
    </if>
    GROUP BY user_id ORDER BY `sum` DESC LIMIT 0, 10
</select>

terrymanu assigned tuohai666 Mar 21, 2019

terrymanu added the need feedback label Mar 21, 2019

Harper0122 mentioned this issue Mar 25, 2019

Weekly Report of ShardingSphere (2019-3-8 to 2019-3-15) #2085

Closed

tuohai666 mentioned this issue Mar 26, 2019

fix SQL rewrite issue #2086

Merged

tuohai666 pushed a commit that referenced this issue Mar 26, 2019

fix SQL rewrite issue (#2086)

d2a56c5

#2062, fix SQL rewrite issue (#2086)

tuohai666 mentioned this issue Mar 26, 2019

#2062, Wrong LIMIT rewrite while GROUP BY and ORDER BY on different items #2098

Merged

terrymanu closed this as completed in #2098 Mar 26, 2019

terrymanu added a commit that referenced this issue Mar 26, 2019

Merge pull request #2098 from tuohai666/dev

5ac00c3

#2062, Wrong LIMIT rewrite while GROUP BY and ORDER BY on different items

tuohai666 added this to the 4.0.0.M1 milestone Mar 28, 2019

tuohai666 added type: bug and removed need feedback labels Mar 29, 2019

Harper0122 mentioned this issue Apr 1, 2019

Weekly Report of ShardingSphere (2019-3-8 to 2019-3-15) #2145

Closed

7 tasks

tuohai666 mentioned this issue May 10, 2019

When routing to only one table, can it do not rewrite limit? #2360

Closed

tuohai666 mentioned this issue May 22, 2019

limit bug fixed in which released version？ #2419

Closed

tuohai666 mentioned this issue Aug 20, 2019

When use mybatis recent version how to use executeQuery() #2891

Closed

lyflyy mentioned this issue Jun 14, 2021

## Wrong LIMIT rewrite while GROUP BY and ORDER BY #10806

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Wrong LIMIT rewrite while GROUP BY and ORDER BY on different items #2062

Wrong LIMIT rewrite while GROUP BY and ORDER BY on different items #2062

joooohnli commented Mar 20, 2019

tuohai666 commented Mar 20, 2019

joooohnli commented Mar 21, 2019

tuohai666 commented Mar 21, 2019

joooohnli commented Mar 21, 2019

tuohai666 commented Mar 21, 2019

joooohnli commented Mar 21, 2019

tuohai666 commented Mar 21, 2019

tuohai666 commented Mar 26, 2019

Anricx commented Apr 5, 2019 •

edited

Loading

lyflyy commented Jun 14, 2021

Wrong LIMIT rewrite while GROUP BY and ORDER BY on different items #2062

Wrong LIMIT rewrite while GROUP BY and ORDER BY on different items #2062

Comments

joooohnli commented Mar 20, 2019

Bug Report

Which version of ShardingSphere did you use?

Which project did you use? Sharding-JDBC or Sharding-Proxy?

Expected behavior

Actual behavior

Reason analyze (If you can)

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

Example codes for reproduce this issue (such as a github link).

tuohai666 commented Mar 20, 2019

joooohnli commented Mar 21, 2019

Expected behavior

Actual behavior

tuohai666 commented Mar 21, 2019

joooohnli commented Mar 21, 2019

tuohai666 commented Mar 21, 2019

joooohnli commented Mar 21, 2019

tuohai666 commented Mar 21, 2019

tuohai666 commented Mar 26, 2019

Anricx commented Apr 5, 2019 • edited Loading

lyflyy commented Jun 14, 2021

I also had this issue in 【4.1.1】

Bug Report

Which version of ShardingSphere did you use?

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

Expected behavior

Actual behavior

Reason analyze (If you can)

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

Example codes for reproduce this issue (such as a github link).

Anricx commented Apr 5, 2019 •

edited

Loading