Tag not being created after upgrade from 9i to 10g

Question

We're upgrading from 9i to 10g - about time - and we've hit some "unexpected behaviour".
If I run
    SELECT  xmlelement("TestMsg",
                    XMLFOREST(m.tx_id   "MsgNum",
                              m.tx_type "MsgTyp"
                              ) MESSAGE -- this is the alias for the XMLFOREST item
                    ) ut_xml
    FROM (select 1 tx_id, 'test' tx_type from dual) mon my 9.2.0.4 database I get
<TestMsg>
  <MESSAGE>
    <MsgNum>1</MsgNum>
    <MsgTyp>test</MsgTyp>
  </MESSAGE>
</TestMsg>- an extra tag is created based on the alias of the XMLFOREST item.
on my 10.2.0.4 database I get
<TestMsg>
  <MsgNum>1</MsgNum>
  <MsgTyp>test</MsgTyp>
</TestMsg>no MESSAGE tag.
Some of the XML parsing we have is taking account of this MESSAGE tag and hence is now breaking.
I guess my question is whether we've messed up the install of XMLDB or whether the 9i behaviour was incorrect and we should amend the parsing to the 10g behaviour.

Answer 1

Behavior change...?
SELECT  xmlelement("TestMsg",
                    xmlelement("MESSAGE",
                    XMLFOREST(m.tx_id   "MsgNum",
                              m.tx_type "MsgTyp"
                    )) ut_xml
FROM (select 1 tx_id, 'test' tx_type from dual) m
will give output in 10.2.0.4.0 EE
UT_XML
<TestMsg>
   <MESSAGE>
      <MsgNum>1</MsgNum>
      <MsgTyp>test</MsgTyp>
   </MESSAGE>
</TestMsg>Edited by: Marco Gralike on Mar 29, 2011 1:07 PM