Handling XML data in Dreamcoder

Newsletter Subscription | Glossary | Contact Us

Home > All Categories > Oracle > DreamCoder for Oracle > Handling XML data in Dreamcoder

Handling XML data in Dreamcoder

Authored by: Peter Boekelaar
Viewed: 768 times so far

The use of XML

XML is more and more the way to interact between databases. There are a lot of companies where XML has become the standard of exchanging data, even between two schemas on the same database. I personally agree on using XML between databases, as long as it is done because the DB's are on different locations, use a different OS, or because it is data exchange between an Oracle and MySQL or other DB.

Editing and storing XML in tables

Off course these XML messages must be stored in tables. The two most common ways to do that is within a CLOB or an XMLType. Using a CLOB has a few advantages above XMLType, for instance the possibility to concatenate XML, and the fact that you don't need a root element or the fact that the XML has to be valid.

But the XMLType is the most common way to store your XML. You can validate your message against a stored XML schema, and you can easely update or extract values in your XML message.

XML and Dreamcoder

CLOB: The datagrid of Dreamcoder supports the use of CLOB's, although the interface could be more sufficient. The interface for showing CLOB data is not really consistent and easy. There is an option for using/showing a popup editor for CLOB's, but that option only works with editable grids. The result grid of a query does not support popup editors on CLOB's. It shows data just by hovering your mouse over the clob column. then a hint is shown with (a part of) the content. If large CLOB's are queried, the result data cannot be shown completely. maybe a readonly popup editor could be used? Even better would be the use of an MDI Child with a (readonly) editor, only shown when doubleclicking the CLOB field, instead of hovering over with your mouse. As far as I am concerned this is a major issue on querying and/or modifying data.
XMLType: Since Oracle 11g is a fact, XML becomes more and more a standard way of storing data, so I think it is a must to support the Oracle XMLType in grids. Most of the time the XML data in the XMLType is formatted, so a popup editor working the same the popup editor on CLOB's would be nice. Even nicer would be an editor that makes it possible to format unformatted XML. Since an XMLType only contains valid XML, it must be easy to format the contains of an XMLType to XML.

Click Here to View all the questions in DreamCoder for Oracle category.

File Attachments

There are no attachment file(s) related to this question.

User Comments

alcoh1002@mail.ru on Wed, Feb 13th, 2008 at 5:32 AM
Greetings to everyone !! You www.sqlplex.com always interestingly. Just in a theme. It is better, than to write the report about ,undoubtedly. Bye!So long!