GitHub user xjlgod added a comment to the discussion: 同一个服务多数据源操作，针对同一个数据源的分支事务进行合并
Currently, in AT mode, separate branch transactions are created and can function normally, but in XA mode, does it throw errors due to non-reentrancy? I reviewed the dynamic data source PR(https://github.com/baomidou/dynamic-datasource/pull/316), which essentially unified connection management for commit and rollback. Can XA mode be modified, but is it necessary for AT mode? Or can users choose? GitHub link: https://github.com/apache/incubator-seata/discussions/7357#discussioncomment-13234419 ---- This is an automatically sent email for dev@seata.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@seata.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org For additional commands, e-mail: dev-h...@seata.apache.org
