The related topics have already issued two articles in front. Although there are many people reading (the heart is stealing), it is rare comment. I feel very regret. Whether it is tomatoes or stinky eggs, I like it. Many things are more distinguished. Let's write some of my thoughts (the research results are not saying, just think about it):
According to my analysis, the existing Native-XML database has excessively emphasized the processing of the XML document, and ignored the role of the database itself: describes the description and storage of objective things. Therefore, there is no advantage that the business sector involved in the processing of the traditional relational database is not shown, but there will be such a shortcoming.
For the above description, planned
XMLDB should primarily implement the goal (make up for the shortcomings of ordinary databases and solving
The Native-XML database is short):
Based on the description of the database design, different database-based database design, or NXD database based database design, new XMLDB, will be based on the description of the database design, that is, based on the objective things, fully utilize The XML document stores things in a description of the things in a natural language. Increase the concept of the version. Ability to work with different versions of data files. Data distributed storage and powerful aggregation capabilities. The smallest storage unit is not an XML storage unit, but XML DB fragment can store the contents of the same table in different ways, while transparent to the user, using the converter and aggregator, to the user. Still a complete XMLDBData object. Based on multi-threaded data retrieval capabilities, it is possible to quickly find the required data content. With multi-threading, multiple XMLDB fragments of a table can be retrieved simultaneously, and then through the aggregator, aggregate into a complete XMLDBDATA object to implement the quick retrieval of the data. Support XML-based query language (xQuery? Maybe Yes, Maybe No). First achieve a unique, XML-based query method. On this basis, through the transformation, you can provide some of the basic concepts and features of the traditional database, such as data synchronization, lock operation, and operation of the transaction, etc. These are some very classic concepts in the database, which is an indispensable part of a complete database that should be supported and implemented. Provide a complete adapter mechanism to support support for traditional SQL language operations. Provide user-defined function functions. First, users use Java language custom functions, after the technology is mature, provide support for scripting languages. Provide a variety of connection and security solutions. Provide HTTPS, SOAP and other network connection methods, and the database itself is an open interface that can load different security solutions. Provide a wealth of connection and debugging tools (which are optional targets, others will not include in the core components in addition to the command line debugging tool)
Then, the design will be discussed, focusing on implementing those objectives discussed above, I will complete the detailed design of the system design and core modules, and strive to make it into an open source database software, we work together. (The following is mainly referring to XMLDB Java implementation)
