ListenQ commented on issue #30300: URL: https://github.com/apache/shardingsphere/issues/30300#issuecomment-1965651206
> > Is the default transaction rule of ShardingSphere JDBC local? > > * Yes, the following is considered the default value. > > ```yaml > transaction: > defaultType: LOCAL > ``` > > * Obviously, the XA distributed transaction module on Jakarta EE 8 and the Seata AT mode distributed transaction module are optional modules. > > > Are there any demo projects related to ShardingSphere JDBC transactions? > > * Check out https://github.com/apache/shardingsphere/tree/master/examples/shardingsphere-jdbc-example-generator to configure the `examples/shardingsphere-jdbc-example-generator/src/main/resources/config.yaml` file content to generate Example. > * Bonus topic is that the nightly CI for the Example module is broken, you can try to fix it if you're interested - I'm not a FreeMarker expert after all. > * For distributed transaction integration using ShardingSphere JDBC under GraalVM Native Image, refer to unit test in https://github.com/apache/shardingsphere/tree/ab0ed3d581059a0ff18117f30fa48db75f8f5e3b/test/native/src/test/java/org/apache/shardingsphere/test/natived/jdbc/transactions . Okay, thanks. the following is considered the default value ``` transaction: defaultType: LOCAL ``` Why is transaction consistency guaranteed for multiple database operations? How to simulate that local operations on multiple data sources do not meet distributed transaction consistency? -- 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]
