They are both SQL statements used to either commit or undo data transactions.
Wikipedia has a good general explanation (see links below) but depending on which database you use there may be different methods of handling transactions.
Commit: http://en.wikipedia.org/wiki/Commit_%28data_management%29
Rollback: http://en.wikipedia.org/wiki/Rollback_%28data_management%29
rollback command can retrieve deleted data from a table, provided commit has not been performed after deleting the data. both rollback and commit are transaction control statements.
In Oracle, you can insert rows, update rows or delete rows from tables, but the changes are only current to your session. That means that if you insert a row in a table, no other users will be able to see it until you enter a COMMIT command. If you should enter or delete information by mistake, you have the chance to undo your changes by using the ROLLBACK command. The ROLLBACK will undo changes to data since the last COMMIT was executed.
Rollback is lowering the price to an earlier price for an item.
Rollback - novel - has 320 pages.
Rollback - novel - was created in 2007-04.
The error message may be caused by inadequate rollback segments, if a FETCH is carried out after a COMMIT, or if certain programs do not close their cursors after repeated FETCH and UPDATE notifications.
zzz
Class 3 truck with a rollback body? No, it doesn't require a CDL.
Walmart
Rollback curb is shaped like an "s" if you will. Valley curb is typically a "V"-shaped trough.
Yes, you can very definitely use transactions within a trigger in one of two common ways; 1. As with any other use of transactions - to ensure a collection of commands within the trigger are executed in a repeatable way in the event of failure.2. To 'undo' the process that caused the trigger to fire. For example, the trigger might be doing some additional integrity checks and issuing a rollback to undo the initiating update/delete.---------AnswerCome to think of it, I have never seen a commit on triggers. Triggers as you know are a last line defense based on an action that was carried out by an insert,update or delete. Hence, since the trigger exists on the server, and is only fired if one of the above conditions are executed then it seems pointless to use a commit in the trigger. Also commit goes along nicely with transactions where you begin the transaction and if all is well then you issue a commit, else if the transaction fails, then you issue a rollback.
eScape - 2010 Rollback 1-6 was released on: USA: 14 August 2011