Before giving you a detailed introduction to Oracle XML data, let's first let you know about Oracle 11 GB, and then give a comprehensive introduction to Oracle XML data. In Oracle 11g, you can use CLOB or binary to save XML Information, which is highly flexible. Oracle 11g also supports the XML-based Query mechanism, which can also be selected, such as XQuery.
XQuery is a group of W3C standards for Oracle XML data query and search. It is relatively simpler and more intuitive than directly operating XML. Speaking of Oracle XML data processing enhancements, it is worth mentioning that Oracle 11g began to support JSR 170, which is a set of Java-based content storage warehouse APIs. Oracle 11g provides binary XML support, meaning that in actual use, users can embed XML into PL/SQL for use, you can also integrate PL/SQL into XML.
In Oracle 11g, a new data type is added, called simple_integer. This new integer type has a non-null attribute, which is faster than PLS_INTEGER in terms of processing speed. In addition, the data table feature, known as Virtual Columns, is also supported in 11g. This mechanism allows you to define data table columns based on actual business functions to create more complex and flexible data tables. Oracle 11g supports a new partitioning scheme, allowing you to partition based on time, for example, separating new data content within a certain time interval, this further improves the flexibility of the Oracle database partitioning mechanism.
In addition, Oracle 11G has made many improvements in data tables, such as enhanced read-only data tables, binding multiple triggers to a table, and setting the order of these triggers.
On-site Oracle 11g hot Patching
When XML was launched, no database manufacturer may have paid enough attention to this technology. However, XML has begun to have a huge impact on data storage. XML is widely used in data exchange and storage as a standard in the Internet application field. The development process of the next-generation database will inevitably leave the XML footprint.
XML has an obvious advantage in data storage, that is, you can directly write logical relationships in XML files. To integrate XML into mainstream database engines, the first thing to do is how to output existing relational data into XML format. Currently, some databases can directly convert SQL query results into XML, so that applications can directly use these XML file results as the content output source. On this basis, importing existing documents and data to the database through XML is also an important aspect of the problem, and this work is undoubtedly much more complicated.
In fact, it is not difficult to import documents in XML format into the database, because the XML file has internal logic and specifications, and the difficulty lies in converting different documents into XML files. Of course, the Data Query work also needs to be changed accordingly. It is difficult to guarantee the efficiency simply by relying on SQL query in XML-supported databases. There are two completely different ways to achieve the integration of traditional databases and XML, one way is that database vendors can write more converters and tools to achieve the interaction between traditional database entities and Oracle XML data, oracle XML data will be viewed as one of the various data forms. Another approach is to fully include support for Oracle XML data at the bottom of the database engine, it even designs and builds database products based on XML.
I don't know how many database vendors have the courage to adopt the latter strategy. Of course, this also depends on how much XML will grow in data storage and performance fields. However, it is certain that the support for XML will bring enough return to the database vendor. Therefore, we will see a lot of XML words in the new database software features of each vendor.
- How to completely uninstall Oracle
- Classic description of the Oracle SMON Process
- Oracle routine for beginners
- Two Methods for Oracle data comparison
- A brief summary of Oracle Learning Process