Windows 11.
Created a new table using DDL below which is modeled after an existing table TB_UT_UTBAGS with only 2 columns.
Unique names are DIFFERENT from original TABLE, NESTED TABLE, INDEX.
Two types not provided are DDL for: type UTBAG, and UTBAG_ARRAY_NT table of UTBAG.
Next, open new TB_NESTED_UTBAGS in the table editor.
#1: ORA-32795: cannot insert into a generated always identity column.
SQLDEV should block me from entering data into column UNQID given it's GENERATED ALWAYS declaration.
#2 Attempt to add data into the NESTED TABLE COLUMN is blocked because the Single Record View is READ-ONLY.
In everyday use, it is the User's responsibility to ensure that the entered data is well-formed which would not cause an error; even when the column is a NESTED TABLE COLUMN.
OPINION: A READ-ONLY dialog seems unreasonable, either fully permit data entry, or completely block by disabling the action +INSERT.
#3 BUG: Image shows that I am editing one table name in the DDL.
Exceptions are shown for a different table in RED which I am NOT EDITING. This is a bug.
CREATE TABLE "NEO"."TB_NESTED_UTBAGS"
( "UNQID" NUMBER(*,0) GENERATED ALWAYS AS IDENTITY MINVALUE 1 MAXVALUE 9999999999999999999999999999
INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE NOKEEP NOSCALE NOT NULL ENABLE,
"BAGS_NT" "NEO"."UTBAG_ARRAY_NT"
)
NESTED TABLE "BAGS_NT" STORE AS "NT_UTBAGS"
(PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
NOCOMPRESS
TABLESPACE "USERS") RETURN AS VALUE;
/* Table "NEO"."TB_NESTED_UTBAGS" created.*/
CREATE UNIQUE INDEX "NEO"."IX_NESTED_UTBAGS" ON "NEO"."TB_NESTED_UTBAGS" ("UNQID");
/* INDEX "NEO"."IX_NESTED_UTBAGS" created. */
ALTER TABLE "NEO"."TB_NESTED_UTBAGS" ADD CONSTRAINT "PK_NESTED_UTBAGS" PRIMARY KEY ("UNQID")
USING INDEX "NEO"."IX_NESTED_UTBAGS" ENABLE;
/* Table "NEO"."TB_NESTED_UTBAGS" altered. */
