Bernhard S
Member³
Hello,
I'm using the current version 7.1.5.1397. It seems there's a bug with compares of constraints where on the source side the constraint has a real name while on the target source side it is named with a default "SYS_%". When doing a compare, pl/sql developer just creates a:
alter table TA_BENUTZER_GRUPPE
add constraint UQ_BENUTZER_GRUPPE unique (A_BENUTZER_GRUPPE_NAME)
using index ...
Any drop constraint sql is missing. Consequently when trying to apply the changes, you get a:
ORA-02261: such unique or primary key already exists in the table
If you do the compare in reverse direction it generates:
alter table TA_BENUTZER_GRUPPE
drop constraint UQ_BENUTZER_GRUPPE cascade;
This is wrong too. It leaves you without the unique key constraint, while there actually exists one on target site named in default "SYS_%" format.
Thanx for correcting this bug.
Best Regards,
Berny
I'm using the current version 7.1.5.1397. It seems there's a bug with compares of constraints where on the source side the constraint has a real name while on the target source side it is named with a default "SYS_%". When doing a compare, pl/sql developer just creates a:
alter table TA_BENUTZER_GRUPPE
add constraint UQ_BENUTZER_GRUPPE unique (A_BENUTZER_GRUPPE_NAME)
using index ...
Any drop constraint sql is missing. Consequently when trying to apply the changes, you get a:
ORA-02261: such unique or primary key already exists in the table
If you do the compare in reverse direction it generates:
alter table TA_BENUTZER_GRUPPE
drop constraint UQ_BENUTZER_GRUPPE cascade;
This is wrong too. It leaves you without the unique key constraint, while there actually exists one on target site named in default "SYS_%" format.
Thanx for correcting this bug.
Best Regards,
Berny
