WXingSong opened a new issue, #37283: URL: https://github.com/apache/shardingsphere/issues/37283
I am using sharding jdbc version 5.5.1+Seata2.2.0. When Sharding-JDBC is integrated with Seata, all `@Transactional` annotations end up being taken over by Seata and behave the same as `@GlobalTransactional`. However, in real business scenarios, only cross-service operations require global transactions, while simple operations within a single service do not involve cross-database or sharding queries and only need local transactions. How can we achieve different levels of transaction handling in such scenarios so that local transactions inside a single service are not taken over by Seata? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
