Do we need a commit after DDL statements ?

Question

Generally to save the transactions or query results in the database we have a command COMMIT, which we doesn't use generally after DDL statemnts. If anybody knows the reason then please share with me ? Thank you in advance.

Answer 1

0

DDL statements are "autocommited" by design on oracle.

Tools working on oracle like sql developer offer an autocommit mode. Switching off this mode effects only dml statements. DDL statements are always autocommited.

Internal the processing is something like that:

BEGIN
   COMMIT;
   ... DDL ....
   COMMIT;
EXCEPTION
   WHEN OTHERS THEN
     ROLLBACK;
     RAISE;
END;

Thats different to sql server.

answered Jan 06 '10 at 06:56 PM

Christian13467
846 ● 2

AutoCommit is a nice feature, until it bites you in the rear. Use with extreme caution in production environments - regardless of the tool you use.

Jan 06 '10 at 08:21 PM HillbillyToad

(comments are locked)

Answer 2

0

DDL CREATE/ALTER/DROP commands are implicitly committed.

In a session, if you do 100 inserts, 20 updates, and then 1 DROP at the end, all of that work will be committed whether you issue a COMMIT or not.

answered Jan 06 '10 at 11:03 AM

HillbillyToad
1k ● 2

(comments are locked)

Do we need a commit after DDL statements ?

Follow this question

Related Questions