This content has been marked as final. Show 2 replies
If you click on the Help button in the Table editor, under Indexes pane you will see the following caveat:
Creating both an index and primary key constraint on the same column with different names seems to lead to the conditions you mention. If you create just the primary key constraint, or rename the index to match the primary key constraint, no index will appear in the editor per the help caveat noted above.
(Note, however, that this display does not include any indexes related to primary key and unique key constraints.)
Here is a prior forum discussion along the same lines:
Re: 3.1EA2 index edit display bug
SQL Developer Team
+"If you create just the primary key constraint, or rename the index to match the primary key constraint, no index will appear in the editor per the help caveat noted above."+
It is some kind of solution - but for newly created tables only. And it means that I must obey naming rules which SQL Developer ("Edit table" wizard) likes...
But what about hundreds of tables that exists already with different index name and PK constraint name? Renaming PK indexes in all of them sounds not good.
But without doing this they will be not editable in "Edit table" (as soon as I click on "Indexes" page)
Edited by: dz_r on 2012-11-05 22:00