You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by "huyu-tom (via GitHub)" <gi...@apache.org> on 2025/08/09 01:41:50 UTC
[I] The latest version doesn’t support @ShardingTransactionType, which means we can’t dynamically customize the transaction mode. Was there a specific rationale for this change? [shardingsphere]
huyu-tom opened a new issue, #36219:
URL: https://github.com/apache/shardingsphere/issues/36219
(no comment)
--
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: notifications-unsubscribe@shardingsphere.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The latest version doesn’t support @ShardingTransactionType, which means we can’t dynamically customize the transaction mode. Was there a specific rationale for this change? [shardingsphere]
Posted by "john1337 (via GitHub)" <gi...@apache.org>.
john1337 commented on issue #36219:
URL: https://github.com/apache/shardingsphere/issues/36219#issuecomment-3544658525
ShardingTransactionType is an useful feature,reallly don't know why the community remove 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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The latest version doesn’t support @ShardingTransactionType, which means we can’t dynamically customize the transaction mode. Was there a specific rationale for this change? [shardingsphere]
Posted by "terrymanu (via GitHub)" <gi...@apache.org>.
terrymanu closed issue #36219: The latest version doesn’t support @ShardingTransactionType, which means we can’t dynamically customize the transaction mode. Was there a specific rationale for this change?
URL: https://github.com/apache/shardingsphere/issues/36219
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The latest version doesn’t support @ShardingTransactionType, which means we can’t dynamically customize the transaction mode. Was there a specific rationale for this change? [shardingsphere]
Posted by "terrymanu (via GitHub)" <gi...@apache.org>.
terrymanu commented on issue #36219:
URL: https://github.com/apache/shardingsphere/issues/36219#issuecomment-3174649198
What is your version?
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The latest version doesn’t support @ShardingTransactionType, which means we can’t dynamically customize the transaction mode. Was there a specific rationale for this change? [shardingsphere]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #36219:
URL: https://github.com/apache/shardingsphere/issues/36219#issuecomment-3215904485
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The latest version doesn’t support @ShardingTransactionType, which means we can’t dynamically customize the transaction mode. Was there a specific rationale for this change? [shardingsphere]
Posted by "terrymanu (via GitHub)" <gi...@apache.org>.
terrymanu commented on issue #36219:
URL: https://github.com/apache/shardingsphere/issues/36219#issuecomment-3190389822
Please reference 5.x's API, please try to forget 4.x API.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] The latest version doesn’t support @ShardingTransactionType, which means we can’t dynamically customize the transaction mode. Was there a specific rationale for this change? [shardingsphere]
Posted by "huyu-tom (via GitHub)" <gi...@apache.org>.
huyu-tom commented on issue #36219:
URL: https://github.com/apache/shardingsphere/issues/36219#issuecomment-3174952425
When upgrading from 4.x to 5.4 version, @ShardingTransactionType is no longer supported. Instead, a global configuration has been added. For example, you can add the following in yml:
```yml
transaction:
defaultType: BASE
providerType: Seata
```
However, this is a global configuration, meaning all database operations will use BASE transaction mode. But some databases may only need LOCAL mode.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org