2006 ◽  
Vol 11 (5) ◽  
pp. 1192-1196 ◽  
Author(s):  
Meng Xiaofeng ◽  
Wang Xiaofeng ◽  
Xie Min ◽  
Zhang Xin ◽  
Zhou Junfeng

2006 ◽  
Vol 36 (8) ◽  
pp. 785-834 ◽  
Author(s):  
U. Westermann ◽  
W. Klas
Keyword(s):  

Author(s):  
Ying Zhang ◽  
Arjen de Vries ◽  
Peter Boncz ◽  
Djoerd Hiemstra ◽  
Roeland Ordelman

2004 ◽  
Vol 69 (1-2) ◽  
pp. 87-104 ◽  
Author(s):  
Sudhanshu Sipani ◽  
Kunal Verma ◽  
John A. Miller ◽  
Boanerges Aleman-Meza

Author(s):  
Kjetil Nørvåg

The amount of data available in XML is rapidly increasing and at the same time the price of mass storage is rapidly decreasing, and this makes it possible to store larger amounts of data. The contents of a database or data warehouse are seldom static. New documents are created, documents are deleted and, more important, documents are updated. In many cases, one wants to be able to search in historical (old) versions, retrieve documents that were valid at a certain time, query changes to documents, and so forth. (Note that although this process is somewhat similar to general document versioning maintenance, the aspect of time makes possibilities and appropriate solutions different.) The “easiest” way to do this is to store all versions of all documents in the database and use a middleware layer to convert temporal query language statements into conventional statements, executed by an underlying database system (an example of such a system is TeXOR; Nørvåg, Limstrand, & Myklebust, 2003). Although this approach makes the introduction of temporal support easier, it can be difficult to achieve good performance: temporal query processing is in general costly, and the cost of storing the complete document versions can be high. Thus, a temporal XML database system is necessary.


2012 ◽  
Vol 12 (s1) ◽  
pp. S103-S111
Author(s):  
Ying Jin ◽  
Hemal J. Mehta ◽  
Chandrashekar Madalli

Sign in / Sign up

Export Citation Format

Share Document