PLSQL DEVELOPER VERSION 5.1.2.682
It appears that there is a problem with the table creation script for tables that contain a column that is a nested table. From the object browser I selected tables and right-clicked on the table and clicked edit. Then I clicked View SQL to view the script. The nested table clause is missing from the table script. see below.
-- Type used as a column in a table.
CREATE OR REPLACE TYPE Varchar80Table IS TABLE OF VARCHAR2(80);
Script that PLSQL Developer generated:
create table tlh_test_tab
(
CUST_SEQ NUMBER(15) not null,
REP_SEQ_TAB VARCHAR80TABLE
)
TABLESPACE TS
pctfree 10
pctused 40
initrans 1
maxtrans 255
storage
(
initial 64K
minextents 1
maxextents unlimited
);
-- What the script should be:
create table tlh_test_tab
(
CUST_SEQ NUMBER(15) not null,
REP_SEQ_TAB VARCHAR80TABLE
) NESTED TABLE REP_SEQ_TAB STORE AS NESTED_REP_SEQ_TAB3
TABLESPACE TS
pctfree 10
pctused 40
initrans 1
maxtrans 255
storage
(
initial 64K
minextents 1
maxextents unlimited
);
Am I missing something or is this a bug?
Thanks,
Tom Hillson
It appears that there is a problem with the table creation script for tables that contain a column that is a nested table. From the object browser I selected tables and right-clicked on the table and clicked edit. Then I clicked View SQL to view the script. The nested table clause is missing from the table script. see below.
-- Type used as a column in a table.
CREATE OR REPLACE TYPE Varchar80Table IS TABLE OF VARCHAR2(80);
Script that PLSQL Developer generated:
create table tlh_test_tab
(
CUST_SEQ NUMBER(15) not null,
REP_SEQ_TAB VARCHAR80TABLE
)
TABLESPACE TS
pctfree 10
pctused 40
initrans 1
maxtrans 255
storage
(
initial 64K
minextents 1
maxextents unlimited
);
-- What the script should be:
create table tlh_test_tab
(
CUST_SEQ NUMBER(15) not null,
REP_SEQ_TAB VARCHAR80TABLE
) NESTED TABLE REP_SEQ_TAB STORE AS NESTED_REP_SEQ_TAB3
TABLESPACE TS
pctfree 10
pctused 40
initrans 1
maxtrans 255
storage
(
initial 64K
minextents 1
maxextents unlimited
);
Am I missing something or is this a bug?
Thanks,
Tom Hillson