sql事务转账的sql语句_SQL事务

痛定思痛。 2023-03-05 08:29 3阅读 0赞

sql事务转账的sql语句

## SQL | 交易次数 **(**SQL | Transactions**)** ##

A **transaction** may be a unit of labor that's performed against a database. A **transaction** is the propagation of one or more changes to the database. For instance, if you're creating a record or updating a record or deleting a record from the table, then you're performing a **transaction** there on the table. It's important to regulate these **transactions** to make sure the info integrity and to handle database errors.

**事务**可能是针对数据库执行的工作单位。 **事务**是将一个或多个更改传播到数据库。 例如，如果您要创建记录，更新记录或从表中删除记录，那么您将在表上执行**事务** 。 规范这些**事务**以确保信息完整性并处理数据库错误很重要。

Practically, we'll club many SQL queries into a gaggle and we'll execute all of them together as a neighborhood of a **transaction**.

实际上，我们会将许多SQL查询合并到一个小工具中，并将它们作为**事务**的邻域一起执行。

### 交易性质 **(**Properties of Transaction**)** ###

<table> 
 <tbody> 
  <tr> 
   <th>Properties</th> 
   <th>Description</th> 
  </tr> 
  <tr> 
   <td><b>Atomicity</b></td> 
   <td>It guarantees that all activities inside the work unit are finished effectively. Otherwise, the exchange is prematurely ended at the purpose of disappointment and all the past activities are moved back to their previous state.</td> 
  </tr> 
  <tr> 
   <td><b>Consistency</b></td> 
   <td>It guarantees that the database appropriately changes states upon an effectively dedicated exchange.</td> 
  </tr> 
  <tr> 
   <td><b>Isolation</b></td> 
   <td>It empowers exchanges to work autonomously and straightforward to one another.</td> 
  </tr> 
  <tr> 
   <td><b>Durability</b></td> 
   <td>It makes sure that the changes of a committed transaction remain in case of a system failure.</td> 
  </tr> 
 </tbody> 
</table>

<table> 
 <tbody> 
  <tr> 
   <th> 物产 </th> 
   <th> 描述 </th> 
  </tr> 
  <tr> 
   <td> <b>原子性</b> </td> 
   <td> 它保证了工作单元内的所有活动均有效完成。 否则，交换会出于失望的目的而提前结束，并且所有过去的活动都将恢复到以前的状态。 </td> 
  </tr> 
  <tr> 
   <td> <b>一致性</b> </td> 
   <td> 它保证数据库在有效的专用交换后适当地更改状态。 </td> 
  </tr> 
  <tr> 
   <td> <b>隔离</b> </td> 
   <td> 它使交易所能够彼此独立自主地工作。 </td> 
  </tr> 
  <tr> 
   <td> <b>耐用性</b> </td> 
   <td> 它确保在系统故障的情况下保留已提交事务的更改。 </td> 
  </tr> 
 </tbody> 
</table>

### 交易中使用的命令 **(**Commands Used in Transaction**)** ###

Value-based control orders are just utilized with the **DML Commands**, for example, - **INSERT**, **UPDATE** and **DELETE** as it were. While making tables or dropping them we cannot use these commands.

基于值的控制命令仅与**DML命令一起使用** ，例如**-INSERT** ， **UPDATE**和**DELETE** 。 在创建表或删除表时，我们无法使用这些命令。

![SQL Transactions][]

### 1)COMMIT命令 **(**1) The COMMIT Command**)** ###

The **COMMIT** order is the value-based order used to spare changes summoned by an exchange to the database.

**COMMIT**订单是基于值的订单，用于保留通过交换而召集到数据库的更改。

The **COMMIT** order is the value-based order used to spare changes conjured by an exchange to the database. The **COMMIT** order spares all the exchanges to the database since the last **COMMIT** or **ROLLBACK** order.

**COMMIT**订单是基于价值的订单，用于节省由于交换而导致的对数据库的更改。 自上一个**COMMIT**或**ROLLBACK**指令以来， **COMMIT**指令将所有交换保留到数据库中。

The language structure for the **COMMIT** order is as per the following.

**COMMIT**命令的语言结构如下。

COMMIT;

**Example:**

**例：**

We will consider the following STUDENT table:

我们将考虑以下学生表：

<table> 
 <tbody> 
  <tr> 
   <th>ID</th> 
   <th>NAME</th> 
   <th>Phone No.</th> 
   <th>Percent</th> 
  </tr> 
  <tr> 
   <td>12</td> 
   <td>Sanyam Gupta</td> 
   <td>5652156415</td> 
   <td>79%</td> 
  </tr> 
  <tr> 
   <td>43</td> 
   <td>Divyam Singh</td> 
   <td>1522141252</td> 
   <td>85%</td> 
  </tr> 
  <tr> 
   <td>76</td> 
   <td>Diya Sinha</td> 
   <td>4788471154</td> 
   <td>77%</td> 
  </tr> 
  <tr> 
   <td>88</td> 
   <td>Prabhjeet Singh</td> 
   <td>9875545566</td> 
   <td>92%</td> 
  </tr> 
  <tr> 
   <td>70</td> 
   <td>Preena Rajora</td> 
   <td>8700997912</td> 
   <td>65%</td> 
  </tr> 
 </tbody> 
</table>

<table> 
 <tbody> 
  <tr> 
   <th> ID </th> 
   <th> 名称 </th> 
   <th> 电话号码。 </th> 
   <th> 百分 </th> 
  </tr> 
  <tr> 
   <td> 12 </td> 
   <td> Sanyam Gupta </td> 
   <td> 5652156415 </td> 
   <td> 79％ </td> 
  </tr> 
  <tr> 
   <td> 43 </td> 
   <td> Divyam Singh </td> 
   <td> 1522141252 </td> 
   <td> 85％ </td> 
  </tr> 
  <tr> 
   <td> 76 </td> 
   <td> 迪亚·辛哈(Diya Sinha) </td> 
   <td> 4788471154 </td> 
   <td> 77％ </td> 
  </tr> 
  <tr> 
   <td> 88 </td> 
   <td> Prabhjeet Singh </td> 
   <td> 9875545566 </td> 
   <td> 92％ </td> 
  </tr> 
  <tr> 
   <td> 70 </td> 
   <td> Preena Rajora </td> 
   <td> 8700997912 </td> 
   <td> 65％ </td> 
  </tr> 
 </tbody> 
</table>

The following example will delete a record of a student having a percentage 65 and **COMMIT** the changes in the database.

下面的示例将删除一个学生的记录，该学生的百分比为65，并在数据库中**提交**更改。

DELETE FROM STUDENT
    WHERE percent=65%;
    COMMIT;

We will get the following result:

我们将得到以下结果：

### 2)ROLLBACK命令 **(**2) The ROLLBACK Command**)** ###

The **ROLLBACK** order is the value-based order used to fix exchanges that have not as of now been spared to the database. This order must be utilized to fix exchanges since the last **COMMIT** or **ROLLBACK** order was given.

**ROLLBACK**顺序是基于值的顺序，用于修复到目前为止尚未保存到数据库的交换。 自从给出最后一个**COMMIT**或**ROLLBACK**命令以来，必须利用此命令来固定交换。

The punctuation for a **ROLLBACK** order is as per the following.

**ROLLBACK**顺序的标点如下。

ROLLBACK;

Consider the following data table:

考虑以下数据表：

Here if we will first delete the record then will use the **ROLLBACK** command to get back the data deleted.

在这里，如果我们先删除记录，然后将使用**ROLLBACK**命令取回删除的数据。

DELETE FROM STUDENT
    WHERE percent=65%;

This will give an output:

这将给出输出：

Now if we use ROLLBACK command, we will get the following:

现在，如果我们使用ROLLBACK命令，我们将获得以下信息：

ROLLBACK;

### 3)SAVEPOINT命令 **(**3) The SAVEPOINT Command**)** ###

A **SAVEPOINT** is a point in exchange when you can roll the exchange back in a specific way without moving back the whole exchange.

当您可以以特定方式回滚交换而不回退整个交换时， **SAVEPOINT**是交换点。

The sentence structure for a **SAVEPOINT** order is as demonstrated as follows.

**SAVEPOINT**顺序的句子结构如下所示。

SAVEPOINT SAVEPOINT_NAME;

This order serves just in the formation of a **SAVEPOINT** among all the value-based explanations. The **ROLLBACK** order is utilized to fix a gathering of exchanges.

在所有基于值的说明中，此顺序仅用于形成**SAVEPOINT** 。 **ROLLBACK**订单用于固定交易所的集合。

The sentence structure for moving back to a **SAVEPOINT** is as demonstrated as follows.

返回到**SAVEPOINT**的句子结构如下所示。

ROLLBACK TO SAVEPOINT_NAME;

### 4)SET TRANSACTION命令 **(**4) The SET TRANSACTION Command**)** ###

The **SET TRANSACTION** order can be utilized to start a database exchange. This order is utilized to determine attributes for the exchange that follows. For instance, you can indicate an exchange to be perused just or perused compose.

**SET TRANSACTION**顺序可用于启动数据库交换。 该顺序用于确定随后交换的属性。 例如，您可以指示要仔细阅读的交换或仔细阅读的撰写。

The sentence structure for a **SET TRANSACTION** order is as per the following.

**SET TRANSACTION**顺序的句子结构如下。

SET TRANSACTION [ READ WRITE | READ ONLY ];

> 翻译自: [https://www.includehelp.com/sql/sql-transactions.aspx][https_www.includehelp.com_sql_sql-transactions.aspx]

sql事务转账的sql语句

[SQL Transactions]: /images/20230208/ebfc22d4158b4e448023e6b78b55aa18.png
[https_www.includehelp.com_sql_sql-transactions.aspx]: https://www.includehelp.com/sql/sql-transactions.aspx