R. Agrawal, S. Buroff, N. Gehani, and D. Shasha. Object Versioning in Ode. In IEEE Data Engineering, pages 446--455. IEEE Computer Society Press, April 1991.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....application areas that need support on evolutionary development, such as CAD and CASE tools, motivated versions related research. More recently, the concept of version has been spread to other areas, such as concurrent projects, schema evolution, XML, document versions, and hypermedia systems [2, 4, 8, 21]. A good survey on versions model for software configuration management can be found in reference [5] In addition, reference [10] presents a classified list of different kinds of versioning applications, and specific summaries with versioning in hypermedia area. The concept of time may be ....

.... papers about temporal data, query, implementation and design in reference [12] Implementation issues are analyzed by Snodgrass in reference [24] These two concepts, version and time, are mostly treated individually in the literature, which abounds with models for versioned information [2, 3, 5, 9, 13, 20, 28] and temporal data [6, 12, 22, 23, 24, 25] The novelty of this paper is to put them together, with equal and simultaneous treatment. This idea appears previously in an extension proposed by Wuu and Dayal for the OODAPLEX model, as a uniform model for temporal and versioned object oriented ....

Agrawal, R. et al., "Object versioning in Ode", Proc. 7 Int'l Conf. Data Engineering (ICDE), IEEE Computer Society, Tokio, 1991, pp. 446-455.

....isolation from changes by others, groupware systems tend to focus on collaborativeworkspaces [16, 21] The set of issues involved in supporting each is rather different, and consequently we believe groupware, even though related, falls outside of the domain of NUCM. Versioned databases (e.g. ODE [1], TVOO [42] are related to NUCM, since NUCM itself can be viewed as a versioned database. In fact, many of the features of NUCM are shared byversioned databases. However, an important difference exists, which is the presence of a specific repository model and its associated programmatic ....

R. Agrawal, S. Buroff, N.H. Gehani, and D. Shasha. Object versioning in ODE. In Proceedings of the 7th International Conference on Data Engineering, pages 446--455, Kobe, Japan, April 1991.

....each core policy is mapped onto the abstraction layer and discussed in detail. 5.1.1 Checkout Checkin The rst two CM systems, SCCS [Roc75] and RCS [Tic85] pioneered the checkout checkin policy. It has since been the basis for numerous CM systems, including DSCS [Mil97] Gradient [BKR96] Ode [ABGS91] Sablime [Bel97] ScmEngine [CPT97] and SourceSafe [Mic97] The policy focuses on providing version support for individual artifacts and is typically based on the combined use of a repository and a le system. Versions of artifacts are stored in the repository, but users do not have direct ....

....for cooperative applications [DRS96] Especially in the case of distribution, the set of issues involved in supporting each type of workspace is rather di erent. Consequently, groupware, even though closely related, falls outside of the domain of the testbed. Versioned databases (e.g. Ode [ABGS91] TVOO [ROY99] are related to the testbed since the testbed itself can be viewed as a versioned database. In fact, many of the features of the testbed are shared by versioned databases. Nonetheless, an important di erence exists, which is the presence of a speci c repository model and an ....

R. Agrawal, S. Buro, N.H. Gehani, and D. Shasha. Object versioning in Ode. In Proceedings of the 7th International Conference on Data Engineering, pages 446-455, Kobe, Japan, April 1991.

....transactions. These allow users to make hypothetical changes to databases, in the sense that the changes are not visible to other users. 3.2. 4 Versioning The designers of O state that the versioning mechanism they provide is intended to provide only the basic functionality of versions [Agrawal et al. 91] The goal was to encourage the development of versioning policies appropriate for the applications at hand. Configurations, as described in section 0, are not directly supported in O . The versioning mechanism that is used is orthogonal to type, as would be desired, and so versions are an ....

Agrawal, R., Buroff, S.J., Gehani, N.H. & Shasha, D. "Object versioning in Ode" (1991) Proc. IEEE 7th International Conference on Data Engineering, February 1991

....models have been implemented. This report discusses how the temporal data model developed for T Chimera [4] has been implemented on top of the Ode OODBMS [1] In particular, two different approaches to handle temporal data are investigated. The first approach relies on the Ode versioning mechanism [2]; the second one is based on the allocation of special structures for storing temporal data. The main contribution of this work is to show how time can be effectively introduced in a conventional object oriented context. 1 Introduction Conventional database systems do not offer the possibility ....

....data model T Chimera [4] Our discussion is however highly independent from T Chimera and can be adapted to other temporal object oriented data models relying on the attribute timestamping approach. As target OODBMS we consider Ode [1] which supports a powerful versioning mechanism [2]. The choice of Ode as implementation platform is motivated by its support for the common object oriented modeling features, and by its support for a versioning mechanism, since we were interested in investigating the possibility of realizing an attribute timestamping model through a system based ....

[Article contains additional citation context not shown here]

R. Agrawal, S.J. Buroff, N.H. Gehani, D.Shasha. Object Versioning in Ode. In Proc. Seventh IEEE Int'l Conf. on Data Engineering, 1991.

....management system. Although a number of temporal persistent object models have been proposed in the research community [5, 7, 17, 18] little work has been reported on concrete design and implementation of underlying systems. Related works also include researches on version management in ODBMSs [1, 8, 10]. In most ODBMSs, however, versions are created by specific operators designated for version derivation rather than by ordinal updates to objects, and application depen dent semantics is associated with version derivation as exemplified by branches and merges of versions. Moreover, with the ....

....versions are created by specific operators designated for version derivation rather than by ordinal updates to objects, and application depen dent semantics is associated with version derivation as exemplified by branches and merges of versions. Moreover, with the exception of some works [1, 11], most of the version object models stress management of version derivation relationships and are very weak in the temporal aspect of version management. Temporal persistent object management implemented in POST C provides basic functionality for history management of objects, and various ....

R. Agrawal, S. Buroff, N. Gehani and D. Shasha. Object Versioning in Ode. In Proceeding of 7th International Conference on Data Engineering, pages 446--455, April 1991.

....the constraints of its parent class and new constraints can be added. Consequently, constraints can be used to specialize classes, as in 15. In this paper, we will only describe the linear versioning mechanism. O allows the version graph of an object to be a tree; see [4] for details. 16. Implementations may choose not to allow the deletion of specific versions. 17. Violation of a constraint will cause the transaction of which this access is a part of to be aborted and rolled back as in Cactis [29] at a later time, we may provide additional exception handling ....

R. Agrawal, S. J. Buroff, N. H. Gehani and D. Shasha, "Object Versioning in Ode", Proc. IEEE 7th Int'l Conf. Data Engineering, Tokyo, Japan, Feb. 1991.

.... dept dname; void Employee: identify( cout name; O also provides facilities for creating versions of objects [3] and for associating constraints and triggers with objects [11] 3. DESIGN GOALS CQL is designed to allow SQL users a smooth transition from a relational database to the object oriented database Ode. Here are the specific design goals we had for CQL : 1. CQL should look and feel like SQL ....

R. Agrawal, S. J. Buroff, N. H. Gehani and D. Shasha, "Object Versioning in Ode", Proc. IEEE 7th Int'l Conf. Data Engineering, Tokyo, Japan, Feb. 1991.

....manipulate objects. Without OdeFS, we would have to rewrite it, turning file references into O operations and then maintain the rewritten version. Besides OdeFS, the Ode object database provides several object compatible interfaces to Ode that are targeted to different kinds of users: 1. O [1, 2, 4, 8, 9]: A programming interface for programmers, especially C programmers. 2. CQL [7] An interactive SQL like interface for the relational database user. 3. OdeView [3, 6] A user friendly graphical interface for the non programmer. An additional goal is that OdeFS should be ....

R. Agrawal, S. J. Buroff, N. H. Gehani and D. Shasha, "Object Versioning in Ode", Proc. IEEE 7th Int'l Conf. Data Engineering, Tokyo, Japan, Feb. 1991.

....standard language for software development, and database systems based on C have attracted much attention. We provide a detailed description of our implementation with the hope that this paper will serve as a reference for implementors of database systems based on C . 1. INTRODUCTION Ode [6, 7, 9, 18] is a database system and environment based on the object paradigm. Ode offers one integrated data model for both database and general purpose manipulation. The database is defined, queried, and manipulated using the database programming language O , which is an upward compatible extension of the ....

....the core functionality of the language, can be obtained from N. Gehani. Continuing work on O includes the investigation of performance related issues, 10 such as optimization [24] and the incorporation of new facilities into the language. These include support for large objects, versions [9], constraints and triggers [18] We are also studying the use of a persistent type catalog to store information about types of objects in an Ode Database. The design of such a catalog is an interesting open research problem. 8. ACKNOWLEDGMENTS We appreciate the helpful comments of J. Richardson, ....

R. Agrawal, S. J. Buroff, N. H. Gehani and D. Shasha, "Object Versioning in Ode", Proc. IEEE 7th Int'l Conf. Data Engineering, Tokyo, Japan, Feb. 1991.

No context found.

R. Agrawal, S. Buroff, N. Gehani, and D. Shasha. Object Versioning in Ode. In IEEE Data Engineering, pages 446--455. IEEE Computer Society Press, April 1991.

No context found.

Agrawal R., Buroff S., Gehani N.H., and Shasha D., Object versioning in ODE. In Proceedings of the 7th International Conference on Data Engineering, pages 446--455, Kobe, Japan, April 1991.

No context found.

Agrawal, R., Buroff, S., Gehani, N., Shasha, D., "Object versioning in Ode," Proceedings of the 7th IEEE International Conference on Data Engineering, pp. 446455, April 1991.

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