xmltype store as clob or binary xml?
our developers found the problem that a value xmltype stored as securefile binary xml is slightly changed after commit.
they store <?xml version="1.0" encoding="UTF-8" standalone="yes"?> to the xmltype colum and after commit it reads: <?xml version="1.0" encoding="UTF-8" standalone='yes'?>
the change is that the value tag "standalone" is now surrounded by single quotes.
i found out that this change does not happen, when xmltype is stored as securefile CLOB.
so my questions are:
1) why is this tag changed? it looks like no other data of the xml is changed (but formatted)
2) are there relevant advantages to store in binary xml? (performance, space...?)
they store <?xml version="1.0" encoding="UTF-8" standalone="yes"?> to the xmltype colum and after commit it reads: <?xml version="1.0" encoding="UTF-8" standalone='yes'?>
the change is that the value tag "standalone" is now surrounded by single quotes.
i found out that this change does not happen, when xmltype is stored as securefile CLOB.
so my questions are:
1) why is this tag changed? it looks like no other data of the xml is changed (but formatted)
2) are there relevant advantages to store in binary xml? (performance, space...?)
Tagged:
0