linghengqian commented on issue #35892: URL: https://github.com/apache/shardingsphere/issues/35892#issuecomment-3037940418
- You can always consider changing the source code of this optional shardingsphere module. Just like what I refer to in https://github.com/apache/shardingsphere/issues/34556#issuecomment-2633231177, but this requires writing a real integration test. - As we have mentioned, the instance of seata client is globally unique, https://github.com/apache/incubator-seata/issues/6614 does make it impossible for shardingsphere to create integration tests across seata client instances in the master branch, but requires such unit tests to be placed in external git. Just like https://www.yuque.com/linghengqian/meve2v/es8d3a8a18odao7x. - But if you are using spring, spring itself can dynamically switch data sources through spring beans. You can configure two shardingsphere datasources with different `logical database` names. The configuration of the two `logical databases` is roughly the same, except that the transaction configuration is different. The two `logical databases can be configured to use the same shardingsphere metadata, or they can be configured to use independent shardingsphere metadata. - The legendary evangelist of Spring Team has demonstrated similar operations at https://www.youtube.com/watch?v=rt_cUtb8LnQ . Shardingsphere doesn't use spring framework to write unit tests in master branch at all, so do you want to have a similar video or article explaining how to do it? -- 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]
