terrymanu commented on issue #37092: URL: https://github.com/apache/shardingsphere/issues/37092#issuecomment-3533643096
I've carefully read this issue, but several key concepts need clarification to ensure we can have an effective discussion based on common understanding: 1. Clarification on the concept of "global transaction": What exactly do you mean by "global transaction"? In ShardingSphere's context, this concept doesn't exist. You might have your own understanding of global transactions, but this doesn't help me understand the core issue. Please discuss problems from ShardingSphere's perspective to maintain smooth communication. 2. Confusion about Spring transactions: I don't understand why Spring transactions are frequently mentioned in this discussion. ShardingSphere is an independent database middleware that has no relationship with Spring. While Spring implements transactions by calling JDBC interfaces, ShardingSphere does the same - there's no direct connection between them. 3. Suggestion to simplify the problem: Given these conceptual confusions, I suggest we first focus on the core issues: Please describe: What specific technical problem are you encountering? In which aspect does the current ShardingSphere solution fail to meet your requirements? Is the purpose of this issue to solve a concrete problem, or to discuss better design approaches? I look forward to your clarification of these concepts and questions so we can proceed with more productive technical discussion. -- 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]
