linghengqian commented on issue #34556:
URL:
https://github.com/apache/shardingsphere/issues/34556#issuecomment-2633299248
> After Seata is integrated into distributed transactions, adding
@transactional(rollbackFor = Except.class) on the business methods AT this
point will execute the Seata AT process to execute the transaction. However,
there are many scenarios where a single data source is being manipulated and
TransactionType. LOCAL is sufficient. Is there a solution that only executes
the Seata AT Spring transactions process in the case of multiple data sources,
and that @transactional(rollbackFor = Exception.class) executes normal Spring
transactions in the case of a single data source?
- It's hard to say that I know why the current issue needs to be kept open.
Unless you intend to propose a new design solution to the current issue. As you
can see, the unit test of seata client by shardingsphere is a bit weird.
--
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]
