blob: 576e3e3b45b9708b68f2c6d521ab98522cb7a4d2 [file] [log] [blame]
---
title: ROLLBACK
---
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
Aborts the current transaction.
## <a id="topic1__section2"></a>Synopsis
``` pre
ROLLBACK [WORK | TRANSACTION]
```
## <a id="topic1__section3"></a>Description
`ROLLBACK` rolls back the current transaction and causes all the updates made by the transaction to be discarded.
## <a id="topic1__section4"></a>Parameters
<dt>WORK
TRANSACTION </dt>
<dd>Optional key words. They have no effect.</dd>
## <a id="topic1__section5"></a>Notes
Use `COMMIT` to successfully end the current transaction.
Issuing `ROLLBACK` when not inside a transaction does no harm, but it will provoke a warning message.
## <a id="topic1__section6"></a>Examples
To discard all changes made in the current transaction:
``` sql
ROLLBACK;
```
## <a id="topic1__section7"></a>Compatibility
The SQL standard only specifies the two forms `ROLLBACK` and `ROLLBACK WORK`. Otherwise, this command is fully conforming.
## <a id="topic1__section8"></a>See Also
[BEGIN](BEGIN.html), [COMMIT](COMMIT.html), [SAVEPOINT](SAVEPOINT.html), [ROLLBACK TO SAVEPOINT](ROLLBACK-TO-SAVEPOINT.html)