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.
asked Jan 06 '10 at 10:35 AM in Default
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:
Thats different to sql server.
answered Jan 06 '10 at 06:56 PM
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