Upload one or more tables to an ORDS database (I did this using CSV files; haven't specifically tested it with other file formats)
Go into the schema designer, select a table, and click 'Keys'
Remove the current primary key
Click 'OK'
The result is that the schema designer whirrs away as if it's processing something, but never reaches a conclusion. The buttons are all disabled when this happens: the only way I've found of getting out of it is to refresh the schema designer, or to exit it by using the browser's 'Back' button. (This of course means any changes made since the last save are lost.)
It's perfectly reasonable for ORDS to object to a table being left without a primary key, but the user needs to be alerted to this. Ideally, what would happen is that clicking 'OK' after removing the primary key (and not replacing it) would trigger a warning saying that the table must have a primary key, so the 'Keys' dialogue box can't be closed until a new key has been added.
To reproduce this:
The result is that the schema designer whirrs away as if it's processing something, but never reaches a conclusion. The buttons are all disabled when this happens: the only way I've found of getting out of it is to refresh the schema designer, or to exit it by using the browser's 'Back' button. (This of course means any changes made since the last save are lost.)
It's perfectly reasonable for ORDS to object to a table being left without a primary key, but the user needs to be alerted to this. Ideally, what would happen is that clicking 'OK' after removing the primary key (and not replacing it) would trigger a warning saying that the table must have a primary key, so the 'Keys' dialogue box can't be closed until a new key has been added.