Creating Object views using XSU PL/SQL.Please SEE.

Question

Hi,
I am presently using XSU PL/SQL utility with Oracle 9i and using the
DBMS_XMLQuery.newContext(<My Select clause goes here>,and the
DBMS_XMLQuery.getXML()which generates an XML document.
My query is:
I have 2 tables (One master and the other detail table.).
Table : DI_Master
di_num
00001
Table: DI_Details
di_num di_act
00001 ABCD
00001 ANCF
00001 IOPP
Now the XML I'd like is :
<di_num>00001</di_num>
<di_act>
<val>ABCD</val>
<val>ANCF</val>
<val>IOPP</val>
</di_act>
Do I need to create object tables for this,insert data into object tables
and then read this table? It will become an extremely tedious process
I guess an OBJECT view can do what I want.Can anyone please tell me how
to write an object view for the 2 tables please and the get the output as
desired.?

Answer 1

Supposing you have further
nesting of the tables.Then how will you go about doing that.You can have multiple levels of CURSOR expressions (see an example below, not a real-life example, but illustrates the point).
SQL> set long 4000
SQL> select dbms_xmlquery.getXML('select deptno,' ||
  2  'cursor(select empno, cursor(select losal, hisal from salgrade) salgrades '||
  3   'from emp e where e.deptno = d.deptno and rownum < 3) EMPLOYEES ' ||
  4  'from dept d where d.deptno = 10')
  5  FROM DUAL;
DBMS_XMLQUERY.GETXML('SELECTDEPTNO,'||'CURSOR(SELECTEMPNO,CURSOR(SELECTLOSAL,HIS
<?xml version = '1.0'?>
<ROWSET>
   <ROW num="1">
      <DEPTNO>10</DEPTNO>
      <EMPLOYEES>
         <EMPLOYEES_ROW num="1">
            <EMPNO>7782</EMPNO>
            <SALGRADES>
               <SALGRADES_ROW num="1">
                  <LOSAL>700</LOSAL>
                  <HISAL>1200</HISAL>
               </SALGRADES_ROW>
               <SALGRADES_ROW num="2">
                  <LOSAL>1201</LOSAL>
                  <HISAL>1400</HISAL>
               </SALGRADES_ROW>
               <SALGRADES_ROW num="3">
                  <LOSAL>1401</LOSAL>
                  <HISAL>2000</HISAL>
               </SALGRADES_ROW>
               <SALGRADES_ROW num="4">
                  <LOSAL>2001</LOSAL>
                  <HISAL>3000</HISAL>
               </SALGRADES_ROW>
               <SALGRADES_ROW num="5">
                  <LOSAL>3001</LOSAL>
                  <HISAL>9999</HISAL>
               </SALGRADES_ROW>
            </SALGRADES>
         </EMPLOYEES_ROW>
         <EMPLOYEES_ROW num="2">
            <EMPNO>7839</EMPNO>
            <SALGRADES>
               <SALGRADES_ROW num="1">
                  <LOSAL>700</LOSAL>
                  <HISAL>1200</HISAL>
               </SALGRADES_ROW>
               <SALGRADES_ROW num="2">
                  <LOSAL>1201</LOSAL>
                  <HISAL>1400</HISAL>
               </SALGRADES_ROW>
               <SALGRADES_ROW num="3">
                  <LOSAL>1401</LOSAL>
                  <HISAL>2000</HISAL>
               </SALGRADES_ROW>
               <SALGRADES_ROW num="4">
                  <LOSAL>2001</LOSAL>
                  <HISAL>3000</HISAL>
               </SALGRADES_ROW>
               <SALGRADES_ROW num="5">
                  <LOSAL>3001</LOSAL>
                  <HISAL>9999</HISAL>
               </SALGRADES_ROW>
            </SALGRADES>
         </EMPLOYEES_ROW>
      </EMPLOYEES>
   </ROW>
</ROWSET>
1 row selected.
SQL>
Also,isnt it a better option to create a VIEW of the
Select clause and pass a view to the select clause? At the end of the day, you could use whatever you feel comfortable with, provided that it produces your expected output and looks clean. We are just giving you the ideas, how you implement it actually in your situation, depends upon a lot of factors, that only you know about.