Delimiter/Marker inside ddl

Question

Hi
I am using DBMS_METADATA to dump the ddl of database objects into a variables using JDBC. I need to seperate each block so that there is a delimiter/marker after every column, constraint, indexe etc inside ddl. Looking for some sugesstions on how to do this, can I include a dilimeter option within the dbms_metadata.get_ddl(...) statement?
Thanks

Answer 1

That misunderstanding is why posters need to provide very specific examples of what they are trying to do. Samples of all inputs and a sample of the expected output.
Instead of DBMS_METADATA.GET_DDL get SXML instead. That will give you a simplified XML version of the metadata with every element surrounded by begin/end element tags. You can then further process it:
1. using XPATH queries to query the elements you want to process.
2. using an XSLT stylesheet to access and manipulate the elements you want to process (which is what Oracle does to give you the DDL in the examples I posted.
SELECT DBMS_METADATA.GET_SXML('TABLE', 'DEPT', 'SCOTT') FROM DUAL
  <TABLE xmlns="http://xmlns.oracle.com/ku" version="1.0">
   <SCHEMA>SCOTT</SCHEMA>
   <NAME>DEPT</NAME>
   <RELATIONAL_TABLE>
      <COL_LIST>
         <COL_LIST_ITEM>
            <NAME>DEPTNO</NAME>
            <DATATYPE>NUMBER</DATATYPE>
            <PRECISION>2</PRECISION>
            <SCALE>0</SCALE>
         </COL_LIST_ITEM>
         <COL_LIST_ITEM>
            <NAME>DNAME</NAME>
            <DATATYPE>VARCHAR2</DATATYPE>
            <LENGTH>14</LENGTH>
         </COL_LIST_ITEM>
         <COL_LIST_ITEM>
            <NAME>LOC</NAME>
            <DATATYPE>VARCHAR2</DATATYPE>
            <LENGTH>13</LENGTH>
         </COL_LIST_ITEM>
      </COL_LIST>
      <PRIMARY_KEY_CONSTRAINT_LIST>
         <PRIMARY_KEY_CONSTRAINT_LIST_ITEM>
            <NAME>PK_DEPT</NAME>
            <COL_LIST>
               <COL_LIST_ITEM>
                  <NAME>DEPTNO</NAME>
               </COL_LIST_ITEM>
            </COL_LIST>
            <USING_INDEX>
               <INDEX_ATTRIBUTES>
                  <PCTFREE>10</PCTFREE>
                  <INITRANS>2</INITRANS>
                  <STORAGE>
                     <INITIAL>65536</INITIAL>
                     <NEXT>1048576</NEXT>
                     <MINEXTENTS>1</MINEXTENTS>
                     <MAXEXTENTS>2147483645</MAXEXTENTS>
                     <PCTINCREASE>0</PCTINCREASE>
                     <FREELISTS>1</FREELISTS>
                     <FREELIST_GROUPS>1</FREELIST_GROUPS>
                     <BUFFER_POOL>DEFAULT</BUFFER_POOL>
                     <FLASH_CACHE>DEFAULT</FLASH_CACHE>
                     <CELL_FLASH_CACHE>DEFAULT</CELL_FLASH_CACHE>
                  </STORAGE>
                  <TABLESPACE>USERS</TABLESPACE>
                  <LOGGING>Y</LOGGING>
               </INDEX_ATTRIBUTES>
            </USING_INDEX>
         </PRIMARY_KEY_CONSTRAINT_LIST_ITEM>
      </PRIMARY_KEY_CONSTRAINT_LIST>
      <PHYSICAL_PROPERTIES>
         <HEAP_TABLE>
            <SEGMENT_ATTRIBUTES>
               <PCTFREE>10</PCTFREE>
               <PCTUSED>40</PCTUSED>
               <INITRANS>1</INITRANS>
               <STORAGE>
                  <INITIAL>65536</INITIAL>
                  <NEXT>1048576</NEXT>
                  <MINEXTENTS>1</MINEXTENTS>
                  <MAXEXTENTS>2147483645</MAXEXTENTS>
                  <PCTINCREASE>0</PCTINCREASE>
                  <FREELISTS>1</FREELISTS>
                  <FREELIST_GROUPS>1</FREELIST_GROUPS>
                  <BUFFER_POOL>DEFAULT</BUFFER_POOL>
                  <FLASH_CACHE>DEFAULT</FLASH_CACHE>
                  <CELL_FLASH_CACHE>DEFAULT</CELL_FLASH_CACHE>
               </STORAGE>
               <TABLESPACE>USERS</TABLESPACE>
               <LOGGING>Y</LOGGING>
            </SEGMENT_ATTRIBUTES>
            <COMPRESS>N</COMPRESS>
         </HEAP_TABLE>
      </PHYSICAL_PROPERTIES>
   </RELATIONAL_TABLE>
</TABLE>
I thing we may have beat this one to death;)