Feedback deferred constraint is incorrect in sql developer 2.1.0.63.41

Question

In the earlier 2.1.0.63 the set contraint didnt work entirely in sql developer.
In this new release the set constraint can be executed and it works, however when you violate a constraint there is no feed back.
example:
I create the following table and insert 2 rows
CREATE TABLE d_orafout
( code NUMBER CONSTRAINT d_codepk PRIMARY KEY DEFERRABLE,
message VARCHAR2(50))
INSERT INTO d_orafout VALUES(904,'invalid table name')
INSERT INTO d_orafout VALUES(903,'invalid column name')
Then i execute:
set constraint d_codepk deferred;
set succeeded.
Then an update that violates the primary key:
update d_orafout set code = 903 where message = 'invalid table name';
1 rows updated
Then when i commit i should get the following error (which works fine in SQL*Plus):
ORA-02091: transaction rolled back
ORA-00001: unique constraint (NWG806.D_CODEPK) violated
However the commit gives me the following output:
commit;
commited
The transaction is not commited, it is rolledback but i dont get the error i need.

Answer 1

Hi <please supply your name>,
Thanks for this feedback,
I have replicated this issues and I have logged a bug.
Bug 9201183 - COMMIT REPORTING COMMIT INCORRECTLY WHEN USED WITH SET CONSTRAINT DEFERRED
Regards,
Dermot.
SQL Developer Team