RENAME instead of DROP/CREATE constraints

[BRi-17]

Hello,

if you are in the edit table mode and change the name of a primary key or unique key in tab "keys", the developer creates 2 sql commands for drop and recreate the key. The drop is executing as CASCADE!! Thereby you implicitly drop all referencing foreign keys by one click without any warning...

Can you please change this statement into RENAMING of the constraint?

Thanks in advance!

 

[Marco Kalter]

I have added this to the list of enhancement requests.