BUG: Wrong DDL for partitioned Index Organized Tables

[BWendling]

If you create a range partitioned index organized table, the "View SQL" function wrongfully places the "organization index" clause below the partitiong information. This clause belongs before the partitioning info.

Example:
create table TEST
(
SORTID NUMBER(4),
VALUE VARCHAR2(25),
constraint TEST_PK primary key (SORTID)
)
organization index
partition by range (SORTID)
(
partition TEST values less than (1)
)

"View SQL" shows:
-- Create table
create table TEST
(
SORTID NUMBER(4) not null,
VALUE VARCHAR2(25),
constraint TEST_PK primary key (SORTID)
)
partition by range (SORTID)
(
partition TEST values less than (1)

)
organization index;

 

[Marco Kalter]

We'll fix it.

 

[bcoulam]

While you're at it, I'd appreciate it if you'd fix the reverse engineer (behind "View SQL" and drag-drop|DDL) to get the DDL for composite partitioned tables correctly.

Using the new DBMS_MetaData hook I can finally get accurate DDL, but it's nasty (everything wrapped in double-quotes, every system-named subpartition shown, etc.) I'd much rather see your reverse engineer engine produce clean, accurate DDL for partitioned items.