You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although issue#29947 has been fixed, these testcases still triggered the problem.
JZuming
changed the title
TiDB produces different results for SELECT statement when using transaction
TiDB produces different results for SELECT statement when using transaction which uses update stmt
Dec 3, 2021
The count column processor of unistore is implemented incorrectly here, it always count the first column (c_ymgvrd in your case), that's why you got 39. @JZuming can you test tidb with tikv? Unistore is only for test purpose.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Setup the environment:
mysql_bk.sql:
mysql_bk.sql.txt
Testcase 1
Testcase 2
2. What did you expect to see? (Required)
The outputs of SELECT statements in Testcase 1 and Testcase 2 are same.
3. What did you see instead (Required)
Output of SELECT statement in Testcase 1
Output of SELECT statement in Testcase 2
Their results are different.
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: