D. S. Batory, J. R. Barnett, J. F. Garza, K. P. Smith, K. Tsukuda, B. C. Twichell, and T. E. Wise. GENESIS: An Extensible Database Management System. IEEE Trans. on Software Engineering, 14(11):1711--1730, 1988.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....goals in mind: simplifying the task of creating new database management systems and enabling the creation of database management systems tailored for specific applications. An early example of this work was the Genesis DBMS toolkit by Batory, Barnett, 18 Garza, Smith, Tsukuda, Twitchell and Wise [6]. The authors sought to understand the interconnection of low level DBMS features such as concurrency control, storage allocation and collection management so that these components could be treated in a modular way and interchanged without affecting correctness. The successor to this work has been ....

D. Batory, J. Barnett, J. Garza, K. Smith, K. Tsukuda, B. Twichell, and T. Wise. Genesis: An extensible database management system. In S. Zdonik and D. Maier, editors, Readings in Object-Oriented Database Systems. Morgan Kaufman, 1990.

....found in traditional DBMS, and include more specialised features which maximise performance. Such systems are very limited to particular applications and most were custom built and remained monolithic. Research has also considered extensible systems to tailor a DBMS to a particular application, [2, 13, 7, 3]. These, though very much in the right direction, were essentially customisable monolithic DBMSs, their architecture being layered resulting in performance overhead problems, which would not suit the types of applications, we wish to focus on. However focus on performance not the only issue. To ....

Batory D., Barnett J., Garza J., Smith K., Tsukuda K., Twichell B., Wise T., 'Genesis: An Extensible Database Management System', in IEEE Transactions on Software Engineering, IEEE November 1988

....the fact that Domain Analysis is very hard, we should stress the difficulty of performing the translation of domains into executable code and the organization of this code for further reuse. Few successful examples of domain analysis can be pointed out. One of them is the Genesis system [1], which provided an encapsulation of database knowledge as a collection of C components. The idea of Draco is to provide a framework such that examples as Genesis could be developed and implemented in a network of domains. The Draco PUC machine is an assembly of technologies for supporting the ....

Batory D., Barnett J., et al., Genesis: An Extensible Database Management System, IEEE Trans. on Software Engineering, Vol. 14(11), pp. 1711-1730; Nov. 88.

....Operating Systems How to structure system software such as operating systems and communications has been a topic of study for the last thirty years. Relevant related work from the communications domain includes Streams [20] and the x kernel [16] as well as from other fields such as databases [3] and file systems [21] 14] each of which faced similar problems in module configuration. Although many of the issues are similar, our approach to routing messages through filters based on possibly changing message contents is much more dynamic than most of these systems. Microkernels face the ....

D. S. Batory, J. R. Barnett, J. F. Garza, K. P. Smith, K. Tsukuda, B. C. Twichell, and T. E. Wise. GENESIS: An extensible database management system. IEEE Transactions on Software Engineering, 14(11):1711--1730, November 1988.

....collections. Extended relational databases are relational database systems that have added constructs to handle more complex data types than can be modeled with records of built in base types. Some representative systems are POSTGRES[53, 55, 56, 57, 58, 59] Starburst[28, 29, 45, 54, 61] Genesis[5, 6, 7], and Exodus[15, 16] In general, these systems allow users to define new base types with richer sets of operations than the built in types. For example, a user could define a box type with operations that compute and compare the areas of boxes. However, the goal of these systems is to retain ....

D. S. Batory et al. Genesis: An extensible database management system. IEEE Transactions on Software Engineering, 14(11):1711--1729, November 1988. Also in S. Zdonik and D. Maier, eds., Readings in Object-Oriented Database Systems.

....in the preceding sections, we discuss only the latter two here. Although there have been many extensible database projects, there have been few attempts to capture the primitive structural operations required to implement predicate based search structures. The GENESIS file management interface [BATO85, BATO88] remains the most comprehensive framework to date. However, GENESIS focuses on ease of use for implementors who select from a set of reusable software components. By contrast, GiST [HELL95] focuses on identifying the interfaces that simplify the implementation of the components which are most ....

D. Batory, J. R. Barnett, J. F. Garza, K. P. Smith, K. Tsukuda, B. C. Twichell and T. E. Wise, "GENESIS: An Extensible Database Management System," IEEE Trans. on Software Eng. 14, 11 (1988), 1711-1730.

....NODS will share with these adaptive middleware approaches the ability to extend the internal characteristics of the platform and services with meta classes to enable runtime adaptability. Going back to the late 80s and beginning of the 90s, several research projects (e.g. EXODUS[3] GENESIS[6, 8], SHORE[4] PREDATOR[5] had for objective to provide open database management systems. Also there have been recent propositions for designing and building componentized database system over an open infrastructure [26, 19, 20] NODS shares such a generation and componentization approach with these ....

D. Bartory J.R. Barnett J.F. Garza K.P. Smith K. Tsukuda B.C. Twichell T.E. Wise. GENESIS: An Extensible Database Management System. IEEE Transactions on software engineering, 14(11):1711-1729, November 1988.

....services with meta classes to enable runtime adaptability. However, di erent to existing works, we do not add runtime adaptability and extensibility to applications using wrapping techniques. Going back to the late 80s and beginning of the 90s, several research projects (e.g. EXODUS[15] GENESIS[9], SHORE[16] PREDATOR[10] had for objective to provide open database management systems. Also there have been recent propositions for designing and building componentized database systems over an open infrastructure [56, 34, 36] NODS shares such a generation and componentization approach with ....

....compilers was to give to the database system programmer a set of software components which have to be assembled following a given speci cation. Such a speci cation can be thought as a program describing the database management system architecture. The prototype proposed in the Genesis project [9] allowed the construction of mono user and mono transaction database management systems. To conclude, there has been a lot of work related to persistence in several domains. Categorizing and comparing them is not easy and it is sometimes not simple to have a global view of what should be a ....

D. Bartory, J.R. Barnett, J.F. Garza, K.P. Smith, K. Tsukuda, B.C. Twichell, and T.E. Wise. GENESIS: An Extensible Database Management System. IEEE Transactions on software engineering, 14(11):1711-1729, November 1988.

....5. Domain specific knowledge One approach to easing the selection and integration problems is to be problem domain specific. In this approach the library uses the existence of problem domains as an organizational scheme. The work of Batory et al. on database system generation is a nice example [3]. The knowledge about database generation could have been presented in three basic ways. 1. A library full of components for all kinds of domains e.g. graphics, networking, database. You find the components you need to put together a database and write glue to compose them. 2. A library full ....

Batory, D. et. al., GENESIS: An Extensible Database Management System, IEEE Trans of Sfw. Eng., SE-14, pp. 1711-1730, November, 1988.

....following avenues of research are open to me: 1. Codify what is already known about the core domains. Sometimes this is not viewed as acceptable research because it does not create any new knowledge. I believe it provides structure to what we already know and argue [Neighbors92] that work like [Batory88] is much more important than this weeks new but unproven theory. All of the core domains in the computer science literature are ripe for this kind of exploitation. 2. W rk on the form of the general knowledge net describing the structure of the domains. o AI has been working on this for 30 years ....

D. Batory, -- 3 -- "GENESIS: An Extensible Database Management System", IEEE Transactions on Software Engineering, vol. SE-14, no. 11, pp. 1711-1730, November 1988.

....implementors must override one or more of the internal GiST methods. This leaves them with many or all of the pre GiST implementation issues. In this extended abstract, we show how to extend the original GiST design to support applications requiring 1 Note that the toolkit approach (e.g. [BATO88]) helps only marginally here, since the problem we describe is essentially that of implementing new parts for the toolkit. specialized index operations. These applications include: ranked and nearest neighbor search (spatial and feature vector databases) index assisted sampling . ....

D. Batory, J.R. Barnett, J.F. Garza, K.P. Smith, K. Tsukuda, B.C. Twichell and T.E. Wise, "GENESIS: An Extensible Database Management System," IEEE Trans. Software Eng. 14, 11 (Nov. 1988), 1711-1730.

.... system extensible [DBE87] These projects include EXODUS 1 at the University of Wisconsin [Care86a, Carey86c] PROBE at CCA [Daya86, Mano86] POSTGRES at UC Berkeley [Ston86b, Rowe87] STARBURST at IBM Almaden Research Center [Schw86, Lind87] and GENESIS at the University of Texas Austin [Bato88a, Bato88b]. Although the goals of these projects are similar, and each uses some of the same mechanisms to provide extensibility, their overall approaches are quite different. For example, POSTGRES is a complete #################################### This research was partially supported by the Defense ....

Batory, D., et al, "GENESIS: An Extensible Database Management System," IEEE Trans. on Software Eng. 14, 11, Nov. 1988.

....objects, separates type definition from type instantiation, allows explicit specification of relationships between objects, and supports object identities that allows persistent database objects to have an existence independent of their values. Some extensible database projects, such as 2 [12, 17, 39, 44, 45, 48] also have similar goals. O is in the same spirit as the work done in designing database programming languages, such as [7, 10, 19, 37, 43, 46, 47, 49, 52] it strives to be the single language for data definition, data manipulation and general computation to avoid the problems arising out of ....

D. Batory, J. Barnett, J. Garza, K. Smith, K. Tsukuda, B. Twitchell and T. Wise, "GENESIS: An Extensible Database Management System", IEEE Trans. Software Eng., Nov. 1988.

....case, however, we do not have the luxury of top down design. In addition, it does not make sense to have multiple transaction managers operating as peers simultaneously on the same data. There have been several research attempts at constructing extensible DBMSs from a set of integrated components [14, 13]. Mostly, however, the concurrency control still followed standard serializability. We feel that the lack of success for extensible concurrency control for a DBMS arises from the lack of a language for defining extended transaction models and the lack of a mechanism for extracting the necessary ....

....database management is the ability for a DBMS to allow a database administrator to extend the core functionality of the system. This is in contrast to database technology that customizes and assembles pre fabricated components into a tailor made Database Management System, such as genesis [13]. An example of a simple extension is the ability (such as triggers) for a DBMS to allow new functions to be programmed in C or some other available programming language. This ability must naturally be carefully controlled since it poses a security risk for the system. Instead of providing such ....

[Article contains additional citation context not shown here]

D. S. Batory, J. R. Barnett, J. F. Garza, K. P. Smith, K. Tsukuda, B. C. Twichell, and T. E. Wise. genesis: An Extensible Database Management system. In Stanley B. Zdonik and David Maier, editors, Readings in Object-Oriented Database Systems, chapter 7.4, pages 500--518. Morgan Kaufman, San Mateo CA, 1990.

....data model open. In that case, apparently no system can be offered; instead, a toolkit, a collection of powerful tools for building database systems is provided with tools such as a general storage manager or an optimizer generator. Major proponents of this approach are EXODUS [Care86] GENESIS [Bato88], DASDBS [Sche90] and more recently Volcano [Gr94] In retrospect, the first approach seems to have been more successful than the second. Extensibility by data types within a fixed data model has made it into commercial systems such as Illustra [Illu95] where one can now buy data blades for ....

Batory, D.S., J.R. Barnett, J.F. Garza, K.P. Smith, K. Tsukuda, B.C. Twichell, and T.E. Wise, GENESIS: An Extensible Database Management System. IEEE Trans. on Software Engineering 14 (1988), 17111730.

....are correct. We also introduce a configuration support tool that, based on these relations, allows only correct configurations to be created. 1 Introduction The recent research on customizable software components such as operating systems [1, 2, 3, 4] file systems [5, 6, 7] database systems [8, 9, 10], and communication subsystems [11, 12, 13, 14, 15] has demonstrated many advantages of customization. For example, it allows the implementation of a software component to be optimized for the requirements of its users as well as for the characteristics of the execution environment. As a result, ....

....cases. 5.1 Hierarchical approaches A system is constructed as a stack, or directed graph, of modules. Each module typically interacts only with modules immediately above and below it in the hierarchy. Recent examples of this approach are the x kernel [11] Horus [14] the Genesis database system [8], and stackable file systems [5] Some of the approaches require that all modules export an identical interface, e.g. x kernel, while others allow layer specific interfaces, e.g. Genesis. In the systems where all modules export the same interface, any stack of modules would be syntactically ....

D. Batory, J. Barnett, J. Garza, K. Smith, K. Tsukuda, B. Twichell, and T. Wise. GENESIS: An extensible database management system. IEEE Transactions on Software Engineering, SE-14(11):1711--1729, Nov 1988.

....fashion (such as CPU cost, I O cost, the number of processors that can be used for processing a query, special purpose processors available etc. Three basic approaches have been used for developing extensible query optimizers: the generator approach [GD87, Mck92] the building block approach [Bat88] and the modular approach [Loh88, M 89, SR86] Some approaches use rules for expressing transformations and user definable cost estimates for the purpose of pruning the search space. Although conceptually it is useful to think of strategy space generation and search as separate problems, ....

D. Batory. GENESIS: An Extensible Database Management System. IEEE Transactions on Software Eng, Nov. 1988.

No context found.

D. S. Batory, J. R. Barnett, J. F. Garza, K. P. Smith, K. Tsukuda, B. C. Twichell, and T. E. Wise. GENESIS: An extensible database management system. In IEEE Transactions on Software Engineering, November 1988. Also in [Zdo90].

No context found.

D. S. Batory, J. R. Barnett, J. F. Garza, K. P. Smith, K. Tsukuda, B. C. Twichell, and T. E. Wise. GENESIS: An Extensible Database Management System. IEEE Trans. on Software Engineering, 14(11):1711--1730, 1988.

No context found.

Batory, D.S., Barnett, J.R., Garza, J.F., Smith, K.P., Tsukuda, K., Twichell, B.C., and Wise, T.E. "GENESIS: An Extensible Database Management System", in Maier, D., and Zdonik, S. (editors), Readings on Object-Oriented Database Systems, Morgan-Kaufmann, 1990.

No context found.

D. S. Batory, J. R. Barnett, J. F. Garza, K. P. Smith, K. Tsukuda, B. C. Twichell and T. E. Wise. Genesis: An Extensible Database Management System. In S. B. Zdonik and D. Maier, editors, Readings in Object-Oriented Database Systems, Chapter 7.4, pages 500--518. Morgan Kaufmann Publishers, 1990.

No context found.

Batory, D.S.; Barnett, J.R.; Garza, J.F.; Smith, K.P.; Tsukuda, B.C.; Twichell, B.C.; Wise, T.E.: GENESIS: An Extensible Database Management System, Technical Report, TR-86-07, Department of Computer Science, University of Texas at Austin, March 1986.

No context found.

Batory, D.S., J.R. Barnett, J.F. Garza, K.P. Smith, K. Tsukuda, B.C. Twichell, and T.E. Wise, GENESIS: An Extensible Database Management System. IEEE Trans. on Software Engineering, 14, 1988, 1711-1730.

No context found.

D.S. Batory, J.R. Barnett, J.F. Garza, K.P. Smith, K. Tsukuda, B.C. Twichell, and T.E. Wise. GENESIS: An Extensible Database Management System. IEEE Trans. on Software Engineering, 14(11):1711--1730, 1988.

No context found.

D. Batory, J. Barnett, J. Garza, K. Smith, K. Tsukuda, B. Twichell, and T. Wise. Genesis: An Extensible Database Management System. ACM Transactions on Database Systems, 14(11):1711--1729, November 1988.

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