Ozsoyoglu, G. & Snodgrass, R. (1995), `Temporal and real-time databases: A survey', IEEE Trans. On Knowledge and Data Engineering 7(4), 513--532.  Home/Search   Document Details and Download   Summary   Related Articles   Check

.... preserve information, track the history of downloaded documents, and support queries on these documents and their history [18] Various techniques for versioning have also been proposed by database researchers who have focused on problems such as transaction time management of temporal databases [19], support for versions of CAD artifacts in O O databases [12] and, more recently, change management for semistructured information [7] In the past, the approaches to versioning taken by database systems and document management systems have often been different, because of the different ....

....the document element records, a page usefulness interval is initiated as (V start ; now) and later updated at V end . Identifying the data pages that were useful at V i is then equivalent to finding which pages have intervals that contain V i . This problem has been solved in temporal databases [19] with an access method called the Snapshot Index [25, 21] If there were k useful pages at V i , they are located with O(k) effort. These useful pages contain all document elements at V i , however, the elements may be stored out of their logical document order. Therefore, the second step is to ....

G. Ozsoyoglu and R. Snodgrass, "Temporal and Real-Time Databases: A Survey", IEEE TKDE 7(4), pp. 513-532, 1995.

....some RAb G Xc be join compatible. is coherent, then , A NG is coherent. are coherent, then is coherent. 6 Related Work There is quite extensive work in the literature on temporal databases and temporal object oriented databases; we refer especially to the recent surveys [19, 10] and the books [23, 22] 26 Probabilistic extensions to relational databases are also well explored in the literature; see especially [16, 7] for more background and a detailed discussion of recent work on probabilistic relational databases. Recently, more complex data models have been extended by ....

G. Ozsoyoglu and R. T. Snodgrass. Temporal and real-time databases: A survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513--532, 1995.

.... [14] Temporal Databases The management of multiple database versions has received much attention under the topic of transaction time temporal databases [40] A large number of temporal data models was studied and the design space for the relational data model has been exhaustively explored [29]. Clifford et al. 21] classified them as two main categories: temporally ungrouped and temporally grouped. Temporal groups are however difficult to support in the framework of flat relations and SQL. Object oriented temporal models are compared in [32] and a formal temporal object oriented data ....

G. Ozsoyoglu and R.T. Snodgrass, "Temporal and real-time databases: A survey". in Knowledge and Data Engineering, 7(4):513--532, 1995.

....and supporting historical queries on their past contents to the point that, e.g. the current SQL standards lack the basic temporal extensions needed to express and support historical queries. Given the strong application demand and the significant research efforts spent on these problems [1], the lack of current solutions must be attributed, at least in part, to the technical difficulty of introducing temporal extensions into relational databases and object oriented databases. Schema changes represent a particularly difficult and important problem for modern information systems, ....

....to that proposed in [11] but it also provides full support for XML query languages such as XPath and XQuery. Temporal Databases and Grouped Representations. There is a large number of temporal data models proposed and the design space for the relational data model has been exhaustively explored [1]. Clifford et al. 5] classified them as two main categories: temporally ungrouped and temporally grouped. The second representation is said to have more expressive power and to be more natural since it is history oriented [5] TSQL2 [13] tries to reconcile the two approaches [5] within the ....

[Article contains additional citation context not shown here]

G. Ozsoyoglu and R.T. Snodgrass. Temporal and real-time databases: A survey. Knowledge and Data Engineering, 7(4):513--532, 1995.

....multiple temporal dimensions. 1 Data Models with Multiple Temporal Dimensions Valid and transaction times are commonly recognized as the basic (orthogonal) temporaldO8H00w ns ford ata [2] and a variety of issues related these t od imensions have been systematically explored in the literature [3]. In parallel, a consid able e#ort has been dn oted tound; stand hether or not valid and transaction times su#ce to capture all relevant temporal aspects in a natural and #cient ay.In[1] ed efined a ne conceptual d ta mo ith four temporald imensions that refines and extend a number of previous ....

....the attributes VT, ET i ,ET t , AT,and TT respectivelyd enote the valid time, the initiating event time, the terminating event time, the availability time, and hetransactiontimeofstored acts. WHERE and WHEN clauses. Comparisons bet een temporald k008w ns can be supported in t o alternative ays [3]: the first one is to dw l ith temporal and non temporald ata in the WHERE clause; the second one is to constrain purely temporal condO0j ns to appear in an a d hoc WHEN clause. Obviously, to make it possible to check condkkO ns mixing temporal and non temporal d ta, e must allo temporaldlwk; HWw ....

G. Ozsoyoglu and R. T. Snodgrass. Temporal and Real-Time Databases: A Survey. IEEE Transactions on Knowledge and Data Engineering, 7(4): 513--532, 1995. 711, 712 provide suitable clauses and/or keywords to allow the user to obtain relations with a proper subset of temporal dimensions.

....the expression of powerful historical queries in a natural fashion. The conceptual and practical interest of this conclusion is underscored by the fact that expressing temporal queries directly on relational databases had instead proven to be a di#cult problem that required major extensions to SQL [16, 35, 36, 26]. Thus viewing the history of relational tables as XML documents could provide an appealing venue for supporting historical queries on databases. Observe that the publication of the current database as an XML document is actually not required for representing the database history as an XML ....

Ozsoyoglu, G., and Snodgrass, R.T.: Temporal and Real-Time Databases: a Survey. IEEE Trans. on Knowledge and Data Engineering, 7(4) (1995) 513-532

.... may suffer from an unlimited amount of priority inversion time, where priority inversion is a situation in which a higher priority transaction is blocked by a lower priority transaction [28] In the past decade, researchers have proposed various real time concurrency control protocols, e.g. [1, 8, 24, 29, 28, 30, 36], for single site as well as distributed RTDBS. In particular, 8, 28] proposed the idea of priority inheritance, which lets a lower priority transaction inherit the priority of a higher priority transaction which is blocked by the lower priority transaction, to reduce the number of priority ....

....is not greater than 50 of the total number of conflicting transactions, all the conflicting transactions will be restarted and the validating transaction is allowed to enter the write phase and then commit. Otherwise, the validating transaction will be blocked. Although many researchers, e.g. [1, 8, 9, 13, 24, 28, 36], have done excellent research in concurrency control for single site and distributed RTDBS, there is little work in concurrency control for MDRTDBS which is a fast growing and important area. In a MDRTDBS, the mobile network imposes a serious time burden on the performance of a MDRTDBS and it ....

G. Ozsoyoglu and R. Snodgrass. Temporal and Real-Time Databases: A Survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513-532 (1995).

....transactions. The mobile clients issue transactions, called mobile transactions (MT) to access data items at the database server. It is assumed that each MT is a set of data requests (read operations) and each MT is defined with a deadline. Although they are not (soft) real time transactions [OS95], meeting their deadlines is an important performance objective. The requirement may be a statistical one such as 95 of the mobile transactions has to be completed within 5 seconds after the submissions. Transactions, which have missed their deadlines, might still be of some use, but beyond a ....

Ozsoyoglu G. and Snodgrass, R., "Temporal and Real-Time Databases: A Survey", IEEE Transactions on Knowledge and Data Engineering, vol. 7, no. 4, pp. 513-532, 195.

.... reo on veq:#9jc topre1jR e information, trackthe history of downloade docume ts, and supportque11j onthe: docume ts and the9 history [18] VariousteuscF:q9 for veqO#1#c have also be1 prop bydatabase re seabase who have focuse onprobleF such as transaction time manageme t of te: oraldatabase [19], support for veqjjFq of CAD artifacts in O Odatabase [12] and,more ree tly, change managec t forse19q#qc 9OR# information [7] Inthe past,the approache to veqj#RFc take bydatabase systes and docume t managec tsysteF have ofte be1 di#e91 t, be cause ofthe di#e7q t reRO#c 9q ts ....

....came non use9F9 As withthe docume te1j97 tre1q71c a page useOjc 9F inteq al isinitiate as (V start , now) andlate update at Vend . Ide tifyingthe data page that weq use9q at V i isthe ee7 ale t to finding which page have inteq als that contain V i . Thisproble has be9 solve in te9 oraldatabase [19] with anacceR mee dcalle the SnapshotInde [25,21] Ifthe9 weF kuse:9 page at V i ,the are locate with O(k)e9Rq7 Theq useq7 page contain all docume te11RO ts at V i , howe ve9 the ee me ts may be store out oftheO logical docume torde: The:9c 11 the se: ste is to sortthe eecF ts bytheq SPaR ....

G. Ozsoyoglu and R. Snodgrass, "Temporal and Real-Time Databases: A Survey", IEEE TKDE 7(4), pp. 513-532, 1995.

....data, medical informatics. 1. Introduction Time is an important and pervasive concept of the real world and needs to be managed in several different ways: events occur at some time points, certain facts hold during a time period, and temporal relationships exist between facts and or events [1]. Time has to be considered when representing information within computer based systems [2] when querying information about temporal features of the represented real world [3] and when reasoning about time oriented data [4] Researchers in the medical informatics field investigated temporal ....

....definition or the adoption of a set of basic concepts that enable a description of the time oriented clinical world in a sound and unambiguous way. Several suggestions have emerged from generic fields of computer science, such as artificial intelligence, or the knowledge and data management areas [63, 64, 65, 66, 3, 1]. Within medical 3 informatics, this effort has progressed from an ad hoc definition of concepts supporting a particular application to the adoption and the proposal of more generic definitions, supporting different clinical applications [45, 6, 8, 9, 10, 35, 30, 13, 14] For example, the ....

[Article contains additional citation context not shown here]

Ozsoyoglu G, Snodgrass RT. Temporal and real-time databases: a Survey. IEEE Transactions on Knowledge and Data Engineering 1995; 7(4): 513532.

....[12, 13, 5] We believe that a query language for MXML would have to take contexts into account. A potential application of MXML which we are currently investigating concerns the representation of time dependent information. Much work has been carried out in the past on temporal databases [15]. The need to incorporate time information is also present in the case of semistructured data [10] However to the best of our knowledge, no such extension has been considered for XML. There is currently no existing implementation of the ideas presented in this paper. The authors plan to ....

G. Ozsoyoglu and R. T. Snodgrass. Temporal and real-time databases: A survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513-532, August 1995.

....given in Appendices A and B. 2 Related Work To our knowledge, this is the first paper on temporal probabilistic object oriented databases though it derives heavily in inspiration from [18] There is extensive work in the literature on temporal databases and temporal object oriented databases (cf. [34, 23, 43, 42]) Probabilistic extensions of relational databases are also wellexplored in the literature; see especially [31, 20] for more background and a detailed discussion of recent work on probabilistic relational databases. Recently, more complex data models have been extended by probabilistic ....

G. Ozsoyoglu and R. T. Snodgrass. Temporal and real-time databases: A survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513--532, 1995.

....and non real time transactions under different real time supports in the system. Keywords: mixed real time database systems, concurrency control protocols, transaction scheduling 2 1 Introduction Research in real time database systems (RTDBS) has received a lot of interests in the past decade [AG92, B96, BLS87, DSK00, HR00, KWL99, L94, OS95, SKS96, YWLS92]. Transactions in a real time database system are usually associated with deadlines. Any deadline violation of a hard real time transaction may result in a catastrophe, while deadline violations of soft real time transactions might only cause a degraded level of system performance without a total ....

Ozsoyoglu, G. and R. Snodgrass, "Temporal and Real-Time Databases: A Survey", IEEE Transactions on Knowledge and Data Engineering, vol. 7, no. 4, pp. 513-532, 195.

.... management [11] CAD systems[10] and temporal databases [1, 3, 9, 12, 16, 18, 19] Some of the problems occurring in multiversion documents are similar to those of transaction time databases, where object histories are maintained (new objects are added without discarding the old ones) [14]. Using timestamping, various efficient indexing and clustering techniques have been proposed for temporal relations [1, 3, 9, 12, 16, 18, 19] Version management schemes have also been proposed in OODBs; however, they are not designed to support documents and to optimize the retrieval of complex ....

G. Ozsoyoglu and R.T. Snodgrass, Temporal and Real-Time Databases: a Survey, IEEE Transactions on Knowledge and Data Engineering, Vol. 7, No.4, pp. 513-532, 1995.

....transactions. The mobile clients issue transactions, called mobile transactions (MT) to access data items at the database server. It is assumed that each MT is a set of data requests (read operations) and each MT is defined with a deadline. Although they are not (soft) real time transactions [11, 14], meeting their deadlines is an important performance objective. The requirement may be a statistical one such as 95 of the mobile transactions has to be completed within 5 seconds after the submissions. Transactions, which have missed their deadlines, might still be of some use, but beyond a ....

Ozsoyoglu G. and Snodgrass, R. (1995) Temporal and Real-Time Databases: A Survey. IEEE Transactions on Knowledge and Data Engineering, vol. 7, no. 4, p.513-532.

....3 Time and MXML 3.1 Properties of Time Domains Time is an important aspect of all real world phenomena. The real world is dynamic and the facts and phenomena which happen in it occur over time. Various notions of time have been studied in the context of databases over the past two decades [6, 3] concerning the structural model and the properties of time. More specifically, time can be linear in the sense that it advances from the past to the future in a totally ordered fashion, or branching that flows from the past to the future in a tree like way. Concerning time domains, time can be ....

G. Ozsoyoglu and R. T. Snodgrass. Temporal and real-time databases: A survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513--532, August 1995.

....costly operation for applications that maintain time evolving data (data warehouses, temporal databases, etc. A typical temporal record has a key, one or more time varying attributes and a time interval representing the record s time validity. Various temporal join predicates have been proposed ([OS95]) Examples include the T Join (join two records if their intervals intersect) and the more general TE Join (join two records if their keys are equal and their intervals intersect) GS91] Here we examine a generalization of the TE Join (the GTEJ join) which also specifies that joined records ....

G. Ozsoyoglu and R. Snodgrass, "Temporal and Real-Time Databases: A Survey", TKDE 7(4), pp. 513-532, 1995.

.... preserve information, track the history of downloaded documents, and support queries on these documents and their history [18] Various techniques for versioning have also been proposed by database researchers who have focused on problems such as transaction time management of temporal databases [19], support for versions of CAD artifacts in O O databases [12] and, more recently, change management for semistructured information [6] In the past, the approaches to versioning taken by database systems and document management systems have often been di erent, because of the di erent requirements ....

....the document element records, a page usefulness interval is initiated as (V start ; now) and later updated at V end . Identifying the data pages that were useful at V i is then equivalent to nding which pages have intervals that contain V i . This problem has been solved in temporal databases [19] with an access method called the Snapshot Index [25, 21] If there were k useful pages at V i , they are located with O(k) e ort. These useful pages contain all document elements at V i , however, the elements may be stored out of their logical document order. Therefore, the second step is to ....

G. Ozsoyoglu and R. Snodgrass, \Temporal and Real-Time Databases: A Survey", IEEE TKDE 7(4), pp. 513-532, 1995.

....Riverside, CA 92521. tsotras cs.ucr.edu This work was partially supported by NSF (IIS 9907477, EIA 9983445) and the Department of Defense. z Fachbereich Mathematik Informatik, Philipps Universitat Marburg, Germany. seeger Mathematik.Uni Marburg.de 1 join predicates have been proposed ([OS95]) Examples include the T Join (join two records if their intervals intersect) and the more general TE Join (join two records if their keys are equal and their intervals intersect) GS91] Here we examine a generalization of the TE Join (the GTE Join) which also specifies that joined records ....

G. Ozsoyoglu and R. Snodgrass, "Temporal and Real-Time Databases: A Survey", TKDE 7(4), pp. 513-532, 1995.

....Versions are retrieved from an SCCS file via scanning through the file and retrieving valid segments based on their timestamps. Various techniques for versioning have also been proposed by database researchers who have focused on problems such as transaction time management of temporal databases [12], support for versions of CAD artifacts in O O databases [14] and, more recently, change management for semistructured information [3] In the past, the approaches to versioning taken by database systems and document management systems have often been different, because of the different ....

G. Ozsoyoglu and R.T. Snodgrass, Temporal and Real-Time Databases: a Survey, IEEE Transactions on Knowledge and Data Engineering, Vol. 7, No.4, pp. 513-532, 1995.

.... configuration management [10] CAD systems[8] and temporal databases [1, 11, 14, 16, 17] Some of the problems occurring in multiversion documents are similar to those of transaction time databases, where object histories are maintained (new objects are added without discarding the old ones) [7, 12]. Timestamping provides an effective technique to deal with evolving objects in temporal databases However, for version management schemes used the OODBs are not designed to support documents and to optimize the retrieval of complete versions [8, 2] Sophisticated schemes previously proposed for ....

G. Ozsoyoglu and R.T. Snodgrass, Temporal and Real-Time Databases: a Survey, IEEE Transactions on Knowledge and Data Engineering, Vol. 7, No.4, pp. 513-532, 1995.

....are generally defined as the database systems supporting time constrained transactions. The timing constraints are usually expressed in the form of deadlines. If the deadlines cannot be met, the usefulness of completing the transactions and the correctness of the systems will be greatly affected [Best96, Ozso95, Shu92, Son88, Yu94]. One of the most important issues in the design of RTDBS is transaction scheduling which objectives are to satisfy the timing constraint of the transactions and at the same time to maintain database consistency [Bern87, Gray93] Database consistency can be achieved with the use of concurrency ....

G. Ozsoyoglu and R. Snodgrass, "Temporal and Real-time Databases: A Survey", IEEE Transactions on Knowledge and Data Engineering, volume 7, number 4, pages 513-532, 1995.

No context found.

G. Ozsoyoglu and R. T. Snodgrass. Temporal and Real-Time Databases: A Survey. IEEE TKDE, 7(4): 513--532 (1995).

....well as general transaction time relations. Gadia presents a multi dimensional data model which is in turn restricted to a two dimensional data model with valid and transaction time as the dimensions [GY88] In this model, however, only data valid in the past may be stored. For example, it is impossible to store on May 11, 1995 the fact that Employee Kate will be in the Shipping department from September 1, 1995 until February 29, 2000. Therefore, the model does not support fully general bitemporal relations, but supports instead retroactive bitemporal relations. The restriction to retroactive data is inherited from ....

G. Ozsoyoglu and R. T. Snodgrass. Temporal and Real-time Databases: A Survey. IEEE Transaction on Knowledge and Data Engineering, 7(4), August 1995.

....not rely on auxiliary access paths, but may exploit sort orderings to achieve efficiency. 1 Introduction Time is an attribute of all real world phenomena. Consequently, efforts to incorporate the temporal domain into database management systems (DBMSs) have been on going for more than a decade [ OS95, TK96] The potential benefits of this research include enhanced data modeling capabilities and more conveniently expressed and efficiently processed queries over time. Whereas most work in temporal databases has concentrated on conceptual issues such as data modeling and query languages, recent ....

G. Ozsoyoglu and R. T. Snodgrass. Temporal and Real-Time Databases: A Survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513--532, August, 1995.

No context found.

Ozsoyoglu, G. and Snodgrass, R., "Temporal and Real-Time Databases: A Survey", IEEE Transactions on Knowledge and Data Engineering, Vol. 7 , No. 4, August 1995, pp. 513-532.

....and there is still a growing need for research in this area. A special issue of ACM SIGMOD Record in March 1988 has brought attention to this area. There have been numerous papers about RTDBMSs from different aspects. There are a number of survey papers on RTDBMSs in the literature [Ulu 94, Ozs 95, Ram 92, Yu 94] 2.2 Transactions A RTDBMS provides service to transactions. A transaction is a program script query that accesses and manipulates (read write) data items (records files, objects objectbase) in the database. Time Constraints Transactions in an RTDBMS are attached with time ....

....runs and commits before its deadline, assuming that we are dealing with firm deadlines only. Therefore, in general, the performance of a RTDBMS is determined by the ratio of the successfully executed transactions to the total number of transactions, that is called the success ratio [Abb 88, Yu 94, Ozs 95] Another performance metric that aids in assessing the performance of a RTDBMS is the restart ratio. That is the ratio of the number of transactions that are aborted and restarted to the total number of transactions. In the case of nested transactions, the transaction restart ratio cannot be ....

[Article contains additional citation context not shown here]

G. Ozsoyoglu, R. T. Snodgrass, "Temporal and Real-Time Databases: A Survey", IEEE Data and Knowledge Engineering Journal, 1995.

No context found.

Ozsoyoglu, G. & Snodgrass, R. (1995), `Temporal and real-time databases: A survey', IEEE Trans. On Knowledge and Data Engineering 7(4), 513--532.

No context found.

G. Ozsoyoglu and R. Snodgrass. Temporal and Real-Time Databases: A Survey. IEEE Transactions on Knoweldge and Data Engineering, 7(4):513--532, August 1995.

No context found.

G. Ozsoyoglu and R. Snodgrass. Temporal and Real-Time Databases: A Survey. IEEE Transactions on Knoweldge and Data Engineering, 7(4):513--532, August 1995.

No context found.

Gultekin Ozsoyoglu and Richard T. Snodgrass. Temporal and real-time databases: A survey. IEEE Trans. Knowl. Data Eng., 7(4):513--532, 1995.

No context found.

G. Ozsoyoglu and R.T. Snodgrass, Temporal and Real-Time Databases: a Survey, IEEE Transactions on Knowledge and Data Engineering, Vol. 7, No.4, pp. 513-532, 1995.

No context found.

G. Ozsoyoglu and R. T. Snodgrass. Temporal and Real Time Databases: A Survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513--532, 1995.

No context found.

Ozsoyoglu G, Snodgrass RT (1995) Temporal and realtime databases: a survey. IEEE Trans Knowledge Data Eng 7(4):513--532

No context found.

G. Ozsoyoglu and R.T. Snodgrass. Temporal and Real-Time Databases: A Survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513-- 532, 1995.

No context found.

G. Ozsoyoglu and R.T. Snodgrass. Temporal and real-time databases: A survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513--532, 1995.

No context found.

G. Ozsoyoglu and R.T. Snodgrass. Temporal and real-time databases: A survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513--532, 1995.

No context found.

G. Ozsoyoglu and R.T. Snodgrass. Temporal and real-time databases: A survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513--532, 1995.

No context found.

G. Ozsoyoglu and R.T. Snodgrass. Temporal and Real-Time Databases: A Survey. In IEEE Transactions on Knowledge and Data Engineering, Vol.7, No.4, pp.513-532, 1995

No context found.

G. Ozsoyoglu and R. T. Snodgrass. Temporal and real-time databases: A survey. IEEE Trans. on Knowledge and Data Engg., 7(4):513--532, Aug. 1995.

No context found.

G. Ozsoyoglu and R.T. Snodgrass. Temporal and real-time databases: A survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513--532, 1995.

No context found.

G. Ozsoyoglu, R.T. Snodgrass. Temporal and Real-Time Databases: A Survey. IEEE TKDE, 7(4), pp 513-532, Aug. 1995.

No context found.

G. Ozsoyoglu and R. Snodgrass. Temporal and realtime databases: A survey. tkde, 7(4), August 1995.

No context found.

Gultekin Ozsoyoglu and Richard T. Snodgrass. Temporal and real-time databases: A survey. IEEE Trans. Knowl. Data Eng., 7(4):513--532, 1995.

No context found.

G. Ozsoyoglu and R.T. Snodgrass, "Temporal and real-time databases: A survey". in IEEE Transactions on Knowledge and Data Engineering, 7(4):513-- 532, 1995.

No context found.

Gultekin Ozsoyoglu and Richard T. Snodgrass. Temporal and real-time databases: A survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513--532, 1995.

No context found.

Ozsoyoglu G, Snodgrass RT. Temporal and real-time databases: a Survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513-532, 1995.

No context found.

G. Ozsoyoglu and R.T. Snodgrass, Temporal and Real-Time Databases: a Survey, IEEE Transactions on Knowledge and Data Engineering, Vol. 7, No.4, pp. 513-532, 1995.

No context found.

Ozsoyoglu, G., and Snodgrass, R., 1995. Temporal and Real-Time Databases: A Survey. IEEE Transactions on Knowledge and Data Engineering, 7, 4.

No context found.

G. Ozsoyoglu and R.T. Snodgrass, Temporal and Real-Time Databases: a Survey, IEEE Transactions on Knowledge and Data Engineering, Vol. 7, No.4, pp. 513-532, 1995.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC