[shardingsphere] branch master updated: Remove transaction support items document (#22333)

[du...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

duanzhengqiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git


The following commit(s) were added to refs/heads/master by this push:
     new dc094c9f59a Remove transaction support items document (#22333)
dc094c9f59a is described below

commit dc094c9f59aec5a9d039b98ca9fe5a96d47f8d21
Author: ZhangCheng <fl...@outlook.com>
AuthorDate: Tue Nov 22 15:55:19 2022 +0800

    Remove transaction support items document (#22333)
    
    * Add implicit commit transaction document
    
    * Add implicit commit transaction document
    
    * Remove
---
 .../content/features/transaction/limitations.cn.md | 22 ----------------------
 .../content/features/transaction/limitations.en.md | 21 ---------------------
 2 files changed, 43 deletions(-)

diff --git a/docs/document/content/features/transaction/limitations.cn.md b/docs/document/content/features/transaction/limitations.cn.md
index 20d660c342f..1997020cea0 100644
--- a/docs/document/content/features/transaction/limitations.cn.md
+++ b/docs/document/content/features/transaction/limitations.cn.md
@@ -8,27 +8,12 @@ Apache ShardingSphere 希望能够将分布式事务的选择权交给使用者
 
 ## LOCAL 事务
 
-### 支持项
-
-* 完全支持非跨库事务，例如：仅分表，或分库但是路由的结果在单库中；
-* 完全支持因逻辑异常导致的跨库事务。例如：同一事务中，跨两个库更新。更新完毕后，抛出空指针，则两个库的内容都能够回滚。
-
 ### 不支持项
 
 * 不支持因网络、硬件异常导致的跨库事务。例如：同一事务中，跨两个库更新，更新完毕后、未提交之前，第一个库宕机，则只有第二个库数据提交，且无法回滚。
 
 ## XA 事务
 
-### 支持项
-
-* 支持 Savepoint 嵌套事务；
-* PostgreSQL/OpenGauss 事务块内，SQL 执行出现异常，执行 `Commit`，事务自动回滚；
-* 支持数据分片后的跨库事务；
-* 两阶段提交保证操作的原子性和数据的强一致性；
-* 服务宕机重启后，提交/回滚中的事务可自动恢复；
-* 支持同时使用 XA 和非 XA 的连接池；
-* 支持跨多个逻辑库的事务。
-
 ### 不支持项
 
 * 服务宕机后，在其它机器上恢复提交/回滚中的数据；
@@ -36,13 +21,6 @@ Apache ShardingSphere 希望能够将分布式事务的选择权交给使用者
 
 ## BASE 事务
 
-### 支持项
-
-* 支持数据分片后的跨库事务；
-* 通过 undo 快照进行事务回滚；
-* 支持服务宕机后的，自动恢复提交中的事务。
-
 ### 不支持项
 
 * 不支持隔离级别。
-
diff --git a/docs/document/content/features/transaction/limitations.en.md b/docs/document/content/features/transaction/limitations.en.md
index 5975b1d70d0..167699cd178 100644
--- a/docs/document/content/features/transaction/limitations.en.md
+++ b/docs/document/content/features/transaction/limitations.en.md
@@ -9,27 +9,12 @@ Apache ShardingSphere wants to give the user choice of distributed transaction t
 
 ## LOCAL Transaction
 
-### Supported
-
-* Support none-cross-database transactions. For example, sharding table or sharding database with its route result in same database;
-* Support cross-database transactions caused by logic exceptions. For example, update two databases in transaction with exception thrown, data can rollback in both databases.
-
 ### Unsupported
 
 * Do not support the cross-database transactions caused by network or hardware crash. For example, when update two databases in transaction, if one database crashes before commit, then only the data of the other database can commit.
 
 ## XA Transaction
 
-### Supported
-
-* Support Savepoint;
-* PostgreSQL/OpenGauss, in the transaction block, the SQL execution is abnormal，then run `Commit`，transactions are automatically rollback;
-* Support cross-database transactions after sharding;
-* Operation atomicity and high data consistency in 2PC transactions;
-* When service is down and restarted, commit and rollback transactions can be recovered automatically;
-* Support use XA and non-XA connection pool together;
-* Support transactions across multiple logical databases.
-
 ### Unsupported
 
 * Recover committing and rolling back in other machines after the service is down;
@@ -37,12 +22,6 @@ Apache ShardingSphere wants to give the user choice of distributed transaction t
 
 ## BASE Transaction
 
-### Supported
-
-* Support cross-database transactions after sharding;
-* Rollback transaction according to undo log;
-* Support recovery committing transaction automatically after the service is down.
-
 ### Unsupported
 
 * Do not support isolation level.