Locks Options

[Prasanna Rajayya...]

Hello All,

I recently went through a book about locks ,i have a question in it ,so i request you to kindly clarify my question.

question
=====

As per the book , When a DML operation is done an automatic DDL lock is placed in the table . So to test this i created a table insert some rows ,commited and once again i updated the table at this point of time i did not commit the work (so the transaction is not completed) and issued a DDL (drop table) the table was droped . I dont understand why this happend ,Please clarify my question .

Thanks And Regards

[Florin Aparaschi...]

Make sure that your tool (SQL*Plus or something else) is not on auto-commit.

[burleson]

Hi Prasanna,


>> I recently went through a book about locks

I have almost every Oracle book written, I know of no books about locks.

What book? What pages?

***************************************
>> Please clarify my question .

I have no idea what you are asking, sorry.

According to your "test" you were able to drop a table that contained uncomitted updates.

This does not make sense because Table locks perform concurrency control for simultaneous DDL operations so that a table is not dropped in the middle of a DML operation.

DDL is different from DML because DDL cannot be rolled back.

Instead of droping the table, try deleting all of the rows, using DML, not DDL.
DML locks or data locks guarantee the integrity of data being accessed concurrently by multiple users. DML locks help to prevent damage caused by interference from simultaneous conflicting DML or DDL operations. By default, DML statements acquire both table-level locks and row-level locks.