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
How do you come to this conclusion? This requires a git with minimal reproducible unit tests, and the database can be created with testcontainers or h2database.
I have already solved this problem. The reason is that the transactionalReadQueryStrategy property was set to DYNAMIC by default, and I changed it to PRIMARY.
Which version of ShardingSphere did you use?
shardingjdbc 5.5.1
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
Expected behavior
If you perform an insert operation within a transaction and then query the data again, you should be able to retrieve it.
Actual behavior
After performing an insert operation within a transaction,the data cannot be queried subsequently
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).
The text was updated successfully, but these errors were encountered: