P.M. Schwarz, W. Chang, J.C. Freytag, G.M. Lohman, J. McPherson, C. Mohan, and H. Pirahesh, "Extensibility in the Starburst Database System", OODBS 1986.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Databases, and Logic Programming. December 1995. The work of Brodsky was supported in part by NSF RIA grant IRI 9409770, and by Office of Naval Research under prime grant No. N00014 94 1 1153. The work of Wang was supported in part by NSF RIA grant IRI 9409769, and by NSF grant BIR 9404831 [S86], ENCORE [Z89] O2 [D90] ORION [JWKL90] POSTGRESS [SRH90] and Illustra) Object Store [OHMS92] Open OODB [BKG93] and UniSQL. Surprising is that while these systems targeted to a large extent the above mentioned application realms, little was done to address the problem of optimization in the ....

P. Schwarz et al., "Extensibility in the Starburst Database System", Procs. 1986 Intl. Workshop on Object-oriented Database Systems. 1986.

....database style queries on 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 ....

P. Schwarz et al. Extensibility in the Starburst database system. In Proceedings of 1986.

.... to address the needs of this emerging class of applications: EXODUS 1 at the University of Wisconsin [Care85a, Care86] PROBE at CCA [Daya85, Mano86] POSTGRES [Ston86b, Ston86c] at Berkeley, GEMSTONE at Servio Logic Corporation [Cope84, Maie86] STARBURST at IBM Almaden Research Center [Schw86], and GENESIS [Bato86] at the University of Texas Austin. Although the goals of these projects are similar, and each uses some of the same mechanisms to provide extensibility, the overall approach of each project is quite different. For example, POSTGRES will be a more complete database ....

Schwarz, P., et al, "Extensibility in the Starburst Database System," Proceedings of the International Workshop on Object-Oriented Database Systems, Pacific Grove, CA, September 1986.

.... Such projects include EXODUS at the University of Wisconsin [Carey and DeWitt 1985, Carey, et al. 1986b, Carey and DeWitt 1987] PROBE at CCA [Dayal and Smith 1985, Manola and Dayal 1986] POSTGRES at Berkeley [Stonebraker and Rowe 1986, Rowe and Stonebraker 1987] STARBURST at IBM Almaden [Schwarz, et al. 1986, Lindsay, et al. 1987] and GENESIS at UT Austin [Batory, et al. 1986] Although the goals of these projects are similar, and each uses some of the same mechanisms to provide extensibility, the overall approach of each project is quite different. STARBURST, POSTGRES, and PROBE are complete ....

Schwarz, P., et al, "Extensibility in the Starburst Database System," Proceedings of the International Workshop on Object-Oriented Database Systems, Pacific Grove, CA, September 1986.

....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 ....

P. M. Schwarz, W. Chang, J. C. Freytag, G. M. Lohman, J. McPherson, C. Mohan and H. Pirahesh, "Extensibility in the Starburst Database System", Proc. Int'l Workshop Object-Oriented Database Systems, Asilomar, California, Sept. 1986.

....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, ....

P. Schwarz, W. Chang, J. Freytag, G. Lohman, J. McPherson, C. Mohan, and H. Pirahesh. Extensibility in the Starburst database system. In Proceedings of the International Workshop on Object-Oriented Database Systems, pages 85--93, Asilomar, CA, Sep 1986.

....the facility for abstract data types. There are two emerging approaches to providing extensibility in database systems [12] The rst approach considers the data model as xed and implements this data model as a system with well dened interfaces for user extensions as in POSTGRES [153] Starburst [150], Gral [78] and PROBE [115, 132] POSTGRES, Starburst, andGralarebasedonrelationalmodelwhilePROBEisbasedonfunctionalmodel.Ontheother hand, the other approach considers even the data model as varying and a toolkit is provided for the construction of an application specic database system as ....

P. Schwarz et al. Extensibility in the Starburst database system. In IEEE/ACM International Workshop on Object-Oriented Database Systems, pages 85-92, 1986.

....traditional optimization techniques are not sufficient and require considerable re design. There has been extensive work on object oriented and extensible database processing, which led to the development of research prototypes as well as commercially available systems, such as Starburst [S86], ENCORE [Z89] O2 [D90] ORION [JWKL90] POSTGRESS [SRH90] and Illustra) Object Store The work of Brodsky was supported in part by NSF RIA grant IRI 9409770, and by Office of Naval Research under prime grant No. N00014 94 1 1153. y The work of Wang was supported in part by NSF RIA grant ....

P. Schwarz et al., "Extensibility in the Starburst Database System", Procs. 1986 Intl. Workshop on Object-oriented Database Systems. 1986. 19

....Daniel T. Schuh, Computer Sciences Department, University of Wisconsin, 1210 West Dayton Street, Madison, WI 53706. 1. MOTIVATION In the mid 1980 s, several database research groups, responding to the needs of a variety of emerging applications, began to explore extensible database systems [Bato88, Care85, Care90, Daya86, Rowe87, Schw86]. Although different groups have different notions of what extensible means, a common desire is to support a high degree of flexibility for customizing the database system to the user s application. Such flexibility is mostly lacking in today s commercial systems, and attempts to provide it ....

Schwarz, P., Chang, W., Freytag, J.C., Lohman, G., McPherson, J., Mohan, C., and Pirahesh, H., "Extensibility in the Starburst Database System," Proc. Int'l. Workshop on Object-Oriented Database Systems, Pacific Grove, CA, 1986.

....mirrors. In this case, customizability is a necessity. Another example of customizability is a graphic equalizer, a device to tailor music to the taste of the listener. This concept is also applicable to software, and has found application in operating systems [16, 3, 6, 26] database systems [2, 24, 22] and communication services [11, 21, 14, 17, 4] Customization is necessary but not sufficient by itself since it is not practical to build a new instance of a service every time a variation is required. The primary reason is that the number of possible variations can be so large that they cannot ....

P. Schwarz, W. Chang, J. Freytag, G. Lohman, J. McPherson, C. Mohan, and H. Pirahesh. Extensibility in the Starburst database system. In Proceedings of the International Workshop on Object-Oriented Database Systems, pages 85--93, Asilomar, CA, Sep 1986.

....it enables the database to grow, and be queryable, without time consuming manual segmentation of the data. 3 A Prototype Implementation We built a prototype that runs on IBM RISC System 6000 workstations. It integrates and utilizes the extensibility features of the Starburst relational DBMS [8] and the IBM Data Explorer 6000 (DX) scientific visualization product. The user specifies a query by choosing a modality, a study, anatomic structures of interest, and intensity ranges of interest. The system then renders the selected data in 3D in one of several ways (see Figure 1) The user can ....

P. Schwarz, W. Chang, J.C. Freytag, G. Lohman, J. McPherson, C. Mohan, and H. Pirahesh, "Extensibility in the Starburst Database System," Proc. 1986 Int'l Workshop on Object-Oriented Database Systems, Pacific Grove, September 1986, pp. 85-92.

....themselves to theoretical examination in terms of expressiveness and other issues. These features make algebraic specification desirable for a data model retrieval language. In recent years it has become apparent that the relational model is not always the right choice for a particular application [Kent79, Care88a, Schw86], and many new data models have been proposed [Abit88b, Lecl87, Fish87, Maie86c, Bane87, Mano86, Roth88, Sche86, Kupe85, Abit88a] Thus an important open question is this: Exactly how far can the algebraic approach be taken Is it a reasonable way to implement and optimize all data models, or is ....

....data manipulation languages, as it is not obvious how one will support ad hoc queries (or optimize accesses effectively) for such systems [Bloo87, Ullm87] This thesis will address these issues, among others. Another direction in data model evolution, one which has spawned such efforts as [Codd79, Dada86, Sche86, Schw86, Rowe87], is to extend the relational model in some way. A common goal of these efforts (and of this work as well) is to provide better support for complex objects and new data types than that offered by the relational model, while still retaining such important features as a powerful, user friendly, data ....

P. Schwarz, W. Chang, J. Freytag, G. Lohman, J. McPherson, C. Mohan, and H. Pirahesh, "Extensibility in the Starburst Database System," Proc. Intl. Workshop on Object-Oriented Database Sys., Pacific Grove, CA, September 1986.

....software modules that dictate which combinations are correct and providing configuration support tools that allow only correct configurations to be created. 1. Introduction The recent surge of configurable or extensible operating systems [21, 3, 9] file systems [13, 17, 18] database systems [2, 29, 26], and communication subsystems [16, 24, 20, 23] has demonstrated the importance of customization in such services. Customization allows the service implementation to be optimized for the requirements of each application and the execution environment. As a result, the performance of such an ....

P. Schwarz, W. Chang, J. Freytag, G. Lohman, J. McPherson, C. Mohan,and H. Pirahesh. Extensibility in the Starburst database system. In Proceedings of the International Workshop on Object-Oriented Database Systems, pages 85--93, Sep 1986.

....A rule chooser is planned for suggesting the best implementation for any given rule. Different policies to determine when the rules are actually activated similar to the coupling modes of HiPAC rules are also being explored. 2.2. 5 Set Oriented Rules in Starburst The goal of the Starburst project [58, 59, 88, 89, 91, 129] at IBM Almaden Research Center is to build from scratch an extensible DBMS that supports new applications as addressed by the next generation database systems [21] and, at the same time, provide a testbed for the research and experiments of new DBMS technologies. In contrast to other ....

P.M. Schwarz, W. Chang, J.C. Freytag, G.M. Lohman, J. McPherson, C. Mohan, and H. Pirahesh. Extensibility in the Starburst database system. In International Workshop on Object-Oriented Database Systems, pages 85--92, 1986. 167

....and UnNest, to change normalized relations to nested relations and vice versa. Variations on this model include the addition of ordered lists as a type [35] and requirements for tuple keys [2, 127] More recently, extensions to the relational model include the ability to define abstract data types [67, 128, 140]. In extended relational systems fields of tuples may contain objects with abstract types. The abstract types are primitive types in the system thus, although they provide a richer modelling capability for fields of a tuple, the semantics of the database are still based on sets, tuples and the ....

....[59] 2.3. 3 Starburst Starburst is an extensible relational database management system that provides modelling extensibility through the ability to add data types and operations for those types, storage and access methods, and internal processing methods (such as query transformation rules) [64, 128]. The query processing portion of the system works on a query represented as a graph, and processes that query by first parsing the query, rewriting the query using transformation rules, then planning an evaluation strategy for the query [64, 115] The query rewrite stage applies rules with ....

P. Schwarz et al. Extensibility in the Starburst Database System. In Dittrich and Dayal [44], pages 85--92.

....it seems that different applications pose different requirements on these systems. This may be one reason for a current trend emphasizing the flexibility, extensibility and easy customizability of database systems (e.g. Exodus [9, 6] Genesis [3, 4] Postgres [21] Probe [7, 12] Starburst [11, 15]) Although the requirements of the different applications may also differ for schema management and especially schema evolution, flexibility has been included so far only into the runtime system of databases. Thus, the schema management and its schema evolution concept for object oriented ....

P. Schwarz et al. Extensibility in the starburst database system. In Proc. Int. Workshop on ObjectOriented Database Systems, 1986.

....database systems are themselves monolithic: the algorithms that are used to store and retrieve data are hard wired and are rather difficult to change. The need to have extensible database systems, and in turn extensible optimizers, has long been recognized in systems like EXODUS [17] Starburst [43], Genesis [4] and Postgres [49] Rule based query optimizers [25, 28, 30, 31, 33, 36] are among the major conceptual advances that have been proposed to deal with query optimizer extensibility. A primary advantage of rule based optimizers over traditional ones is the ability to introduce new ....

....means of constructing extensible optimizers. The primary advantage of rule based query optimizers is the ability to add new operators and algorithms without a costly rewrite of the entire optimizer. Below, we review a few of the more well known rule based optimizers. The Starburst query optimizer [33, 36, 43] uses rules for all decisions that need to be taken by the query optimizer. The rules are functional in nature and transform a given operator tree into another. The rules are commonly those that reflect relational calculus transformations. In Starburst, the query rewriting phase is different from ....

P. Schwarz, W. Chang, J. C. Freytag, G. Lohman, J. McPherson, C. Mohan, and H. Pirahesh. Extensibility in the Starburst database system. In Proceedings International Workshop on Object-Oriented Database Systems, pages 85--92, Asilomar, September 1986.

....manager with a novel, multi layered transaction facility as a kernel upon which a domain appropriate data model and query layer could be built; this layering was modeled after the RSS RDS separation used in System R. Another important project that started at this time was the IBM Starburst project [Schw86]. Starburst can be classified partly as a component based DBMS, as support for new storage and indexing components was a major goal, but it can also be classified as an extended relational DBMS, as it was still centered on the relational model in terms of both its query language (SQL) and its ....

P. Schwarz et al, "Extensibility in the Starburst Database System," in [Ditt86].

No context found.

P.M. Schwarz, W. Chang, J.C. Freytag, G.M. Lohman, J. McPherson, C. Mohan, and H. Pirahesh, "Extensibility in the Starburst Database System", OODBS 1986.

No context found.

P.M. Schwarz, W. Chang, J.C. Freytag, G.M. Lohman, J. McPherson, C. Mohan, and H. Pirahesh. Extensibility in the Starburst Database System. In Proc. of the IEEE/ACM Intl. Workshop on Object-Oriented Database Systems, pp. 85--92, Pacific Grove, 1986.

No context found.

P. Schwarz, W. Chang, J. Freytag, G. Lohman, J. McPherson, C. Mohan, and H. Pirahesh. Extensibility in the Starburst Database System. In Proc. of the 1st Int'l Workshop on Object-Oriented Database Systems, pages 85--92, 1986.

No context found.

P. M. Schwarz, W. Chang, J. C. Freytag, G. M. Lohmann, J. McPherson, C. Mohan, and H. Pirahesh. Extensibility in the Starburst Database System. In Proc. of the 1st Intl. Workshop on Object-Oriented Database Systems, pp. 85-92, Pacific Grove, September 1986.

No context found.

Schwarz, P.M., Change, W., Freytag, J.C., Lohman, G.M., McPherson, J., Mohan, C. and Pirahesh, H., "Extensibility in the Starburst Database System," Proceedings of the 1986 International Workshop on Object-Oriented Database Systems, Pacific Grove, CA, September 1986.

No context found.

Schwarz, P. et al., "Extensibility in the Starburst Database System." Proceedings of the 1986 International Workshop on Object-Oriented Database Systems, (September 1986) pg. 85.

No context found.

P. Schwarz, W. Chang, J. Freytag, G. Lohman, J. McPherson, C. Mohan, and H. Pirahesh. Extensibility in the Starburst database system. In Proceedings of the International Workshop on Object-Oriented Database Systems, pages 85--93, Asilomar, CA, Sep 1986.

First 50 documents

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