I have been studying XML aspects recently, I sincerely controversy for XML in the powerful vitality of data structure and saving exchange. Although I have just gotten in the database or in terms of XML. But does not hinder my exploration of XML database. I have written some ideas here. I hope that there are people in the same way together. Aging is that I will throw a jade, I hope to be an open source project in the future, breaking the technical monopoly of European and American manufacturers in this regard.
Ok, nonsense, first talk about the concept of XML database. In general, there are two kinds of XML databases, one is a pure XML database, that is, the storage element of the data is the XML structure of the XML, which is usually called the Native-XML database, and the other, the data storage is still usually used. Relational database, but access to XML (in fact, it can be seen as a normal database plus a package that supports XML). I want to describe the previous Native-XML database.
First, I have to admit that my research on the relational database is not deep, basically due to the work needs, in the ASP or VB, the Java program has used some SQL text and SQL Server, Interbase and other lightweight databases. So I summarized the relationship database that needs to be improved, and it is not correct and complete. However, anything is two aspects, not in-depth understanding, and also reduces thinking restrictions, let me have a lot of constraints when designing the XML database, let me have more imagination space. Here, I will listen to the problems I think of the relational database: 1. It is not easy to look for massive data, low performance, especially the full text. Second, data distributed storage is not easy to implement. Third, the data stored in different servers and different locations is not easy to integrate. Fourth, facing more and more XML data, the transformation storage is not enough. V. Not easy to achieve custom field data types. 6. You cannot store an object in the data table. 7. You cannot use the world that is closer to objectively describing data (in the relational database, all data is connected to "relationship"). Eight, limited to vendors, not easy second time, and expand its database's functionality. Nine, the complexity of access. Ten, can not be seamless with existing web. XI, data maintained, in this release of data, is not known by the next version of DB Server.