L. Rowe and M. Stonebraker. The POSTGRES data model. Proceedings of the Intern. Conference on Very Large Data Bases (VLDB'97), pp. 83-96 (1987).  Home/Search   Document Details and Download   Summary   Related Articles   Check

....and object systems extended to support 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. ....

Lawrence A. Rowe and Michael R. Stonebraker. The POSTGRES data model. In Proceedings of the Thirteenth International Conference on Very Large Data Bases, pages 83--96, Brighton, England, September 1987. Also in S. Zdonik and D. Maier, eds., Readings in Object-Oriented Database Systems.

.... entities as objects, despite the fact that OODBs have the potential to be populated with many user de ned arbitrary behaviours, possibly implemented in multiple programming languages (e.g. foreign functions in IRIS [F 87] methods in 1 O 2 [LRV88] and user de ned procedures in POSTGRES [RS87]) In IRIS [F 90] and VISION [CS88] userde ned arbitrary behaviours are treated as database objects. However, they are simply collected under a few system de ned function types, capturing little semantics which might help a new user to understand what they do, or help a former user to relocate a ....

....two behaviours, we might want to consider them both to be instances of some graphical behaviour class, rather than have them classi ed di erently because their signatures di er. 4. according to output type: This is just a special case of the previous alternative, and has been used in POSTGRES [RS87]. The two behaviours: size: MapObject real and salary: employee real have the same output type, but considering them to be instances of the same class does not help with the task of modeling behaviours. 5. behaviour equals type: In the ENCORE model [HZ87] each behaviour is considered to ....

Rowe, L. A. and Stonebraker, M. R. The POSTGRES Data Model. Proc. 87' VLDB Conference, 83-96, 1987.

....of potential applications via some form of extensibility. 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. ....

....host to a workstation) Components of complex objects are viewed as records with bytestring attributes. Objects are passed between the kernel and its clients by copying data between a page oriented kernel buffer and a client provided object buffer. The storage system of POSTGRES [Stonebraker and Rowe 1986, Stonebraker 1987] is based on the use of tuples and relations. Each tuple is identified by a unique 64 bit surrogate that never changes. Tuples are not updated in place. Instead, new versions of modified tuples are inserted elsewhere into the database. A vacuuming process moves old data to an archival disk for ....

[Article contains additional citation context not shown here]

Rowe, L., and Stonebraker, M., "The POSTGRES Data Model," Proceedings of the 13th International Conference on Very Large Data Bases, Brighton, England, 1987.

.... and software management, require the capability to create and access multiple versions of an object [8, 23, 30, 51] Object versions are also important for historical databases, such as those used in accounting, legal, and financial applications, that must access the past states of the database [19, 44]. Support for active databases, such as those used in computer integrated manufacturing, power distribution network management, and air traffic control, requires the capability to attach with objects conditions and actions that are triggered when the conditions are satisfied [21, 50] Finally, the ....

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

[Article contains additional citation context not shown here]

L. A. Rowe and M. R. Stonebraker, "The POSTGRES Data Model", Proc. 13th Int'l Conf. Very Large Data Bases, Brighton, England, Sept. 1987, 83-96.

....manipulating any file storage object. Thus, EXODUS provides weak support for encapsulation and there is no clear support for inheritance at this low level of representation. EXODUS uses hints for the management of metadata. There is no direct communication between objects at this level. POSTGRES [32, 35, 36, 37, 38] is a database system built at the university of California, Berkeley. It supports a data model which is relational but extended with abstract data types, attribute and procedure inheritance. POSTGRES uses a no overwrite storage manager whereby old records remain in the database whenever an ....

L. A. Rowe and M. Stonebraker. The postgres data model. In Proceedings of the 13th International Conference on VLDBs, pages 83--96, 1987.

....is enforced that p 0 and p 00 must have identical values. If this constraint is satisfied then the properties inherited by class C from p 0 and p 00 coincide and the value of the inherited property is the common value of p 0 and p 00 . Such data model is the POSTGRES data model [26, 28]. Approach 4: The properties inherited by class C from p 0 and p 00 coincide to a single property whose value is a subclass of the values of p 0 , p 00 . However, this subclass is not a known y class. This approach is followed by traditional frame based models [14] terminological ....

L. Rowe and M. Stonebraker. The POSTGRES data model. Proceedings of the Intern. Conference on Very Large Data Bases (VLDB'97), pp. 83-96 (1987).

....the high demands of complex applications. As new features to the relational database management system evolved, a new project, namely POSTGRES, was needed. POSTGRES offers substantial additional power to the relational database by supporting a relational data model that is extended to include [RS87] user defined operators and procedures, relation attributes of type procedure, relation inheritance of attributes and procedures, and a powerful production rule system. POSTGRES was finally commercialized by Illustra, now taken over by Informix, in 1992. Major database vendors have followed the ....

L. Rowe and M. Stonebraker. The POSTGRES data model. International Conference on Very Large Databases, 83-96, 1987.

....22] A major strength of these proposals is that they are based on well defined data models. These models, like the relational model itself, comprise a formal description of the data structures of the database and the algebraic operations on these structures. In contrast, object oriented languages [46, 10, 12, 14, 16, 21] are usually defined operationally rather then algebraically or axiomatically. CQL strives to combine the advantages of the structural and operational models. It is based on an object algebra that preserves the closure property of SQL, and applies uniformly to sets of objects, regardless of ....

....types, structured complex objects, and methods. Object SQL also supports inheritance. Functions (methods) are written in a general purpose programming language, for example LISP or C for Object SQL, and PASCAL R for HDBL. Similar operational extensions have been developed for the QUEL language [6, 21]. The languages in this group follow the evolutionary approach of extending the relational model with object oriented functionality. There are some recent SQL extensions that, like CQL , are based on C . Ontologic s SQL [ Ontologic SQL ] is an extension of SQL embedded in C ; an interactive ....

L. A. Rowe and M. R. Stonebraker, "The POSTGRES Data Model", Proc. 13th Int'l Conf. Very Large Data Bases, Brighton, England, Sept. 1987, 83-96.

....on global environmental science [18, 19] Sequoia 2000 differs significantly from REINAS in that while REINAS is driven by real time constraints, Sequoia 2000 was primarily designed for retrospective access with little real time emphasis. Like REINAS, Sequoia 2000 was built around a database [15, 17]. Real time systems employing less sophisticated database technologies have also been developed [3, 6, 16] as well as others that run at much lower data rates [5] One such system, StormCast, collects and archives environmental data primarily for current and forecast use, as well as supporting ....

L. Rowe and M. Stonebraker. The Postgres data model. In Proceedings of the 13th Conference on Very Large Data Bases, pages 83--96, Brighton, England, Sept. 1987.

.... primary focus is to provide a platform for investigation of physical database design in an extensible kernel system as well as for generic query processing over heterogeneous distributed repositories [2, 17] The Concert general architecture is similar to other extensible DBMS such as Postgres [16, 20], DASDBS [19] or Starburst [8] It consists of a kernel system for low level data management and query processing as well as an object manager providing advanced query functionality. The kernel is responsible for the management of individual objects within collections, resource and storage ....

L. Rowe and M. Stonebraker, The POSTGRES data model, Proceedings of the Thirteenth International Conference on Very Large Databases (Brighton, England) , 1987.

....type whose only interface is that provided by the definer of the type. But AQUA does support such types, and does so using the abstraction type constructor, allowing any database object to be described using a single uniform type system. This is similar to the ADT concept provided by Postgres [24], but more general in the sense that any type definable in the AQUA type system can be abstracted into a true encapsulated type, and an abstraction in AQUA is a first class citizen of the type system the abstraction constructor has the same status as any other constructor. The distinction is ....

L. Rowe and M. Stonebraker. The postgres data model. In Proceedings of the Thirteenth Very Large Databases Conference. Morgan Kaufmann Publishers, Inc, 1987.

....for database systems. It may also be said that these applications are the primary force driving the current interest in the object oriented database systems. At present, there is little agreement on one uniform model for design databases, although some recent papers have articulated major needs [1, 5, 7 9, 13 17, 19 21, 24, 25, 28, 29, 32 34]. Consequently, O does not come with a hardwired design database model; instead, it provides facilities with which users can develop customized models that match their needs. In designing O , we have distinguished between primitives and policies. Our design effort has been directed towards ....

....we decided against a built in change notification facility [13] because users can implement such a facility using O triggers. A critical requirement of CAD applications that is addressed by O is support for object versioning. Our design, although inspired by many of the earlier proposals [1, 5, 7 9, 13 17, 19 21, 24, 25, 28, 29, 32 34], differs significantly from them in that we focus on introducing a minimum number of concepts with precise semantics and integrating them seamlessly in a programming language. Object versioning in O is orthogonal to type, that is, versioning is an object property and not a type property. ....

[Article contains additional citation context not shown here]

L. A. Rowe and M. R. Stonebraker, "The POSTGRES Data Model", Proc. 13th Int'l Conf. Very Large Data Bases, Brighton, England, Sept. 1987, 83-96.

....attempt to combine the modelling power of object based programming models with traditional database concepts such as persistence, data sharing, consistency, resiliency and optimized query access. A number of object oriented data models and languages have been proposed ( Shi81] Ban87a] Ban87b] [Row87], Mai87] Lec88] Car88] but no single model or language has emerged as a standard for object oriented databases. Our model supports object identity, abstract data types with 1 type inheritance, and encapsulation of behavior and state, as modelling capabilities present in most ....

....object oriented databases is the extension of the relational model to build complex objects. Early extensions relaxed the first normal form requirement of the relational model, allowing set valued attributes ( Jae82] Dad86] The relational model has also been extended with abstract data types ([Row87], Mai87] Ban87a] Alb85] allowing the modelling of more complex types, where components or attributes of objects can be other database objects. We extend the relational data model similarly, and also succeed in applying relational types of algebraic operations to the model. Our algebra ....

[Article contains additional citation context not shown here]

Lawrence A. Rowe and Michael R. Stonebraker. The POSTGRES Data Model. In Proceedings of the 13th VLDB Conference, pages 83--96, 1987.

....data unavailability because of locking problems. 2. TRANSACTION PROCESSING PERFORMANCE This section explores three tactics relevant to transaction processing performance. 2.1. Fast Path It is common knowledge that TP1 consists of 4 commands in a query language such as SQL [DATE84] or POSTQUEL [ROWE87] together with a begin XACT and an end XACT statement. If an application program gives these commands to the data manager one at a time, then the boundary between the data manager and the application must be crossed in both directions 6 times. Moreover, if the application runs on a workstation and ....

Rowe, L. and Stonebraker, M., "The POSTGRES Data Model," Proc. 1987 VLDB Conference, Brighton, England, Sept. 1987.

No context found.

L. Rowe and M. Stonebraker. The POSTGRES data model. Proceedings of the Intern. Conference on Very Large Data Bases (VLDB'97), pp. 83-96 (1987).

No context found.

L. A. Rowe and M. Stonebraker. The POSTGRES Data Model. In Int. Conf. on Very Large Data Bases, pages 83--96, 1987.

No context found.

Rowe, L. A. / Stonebraker, M. R. "The POSTGRES Data Model" From "Readings in object-oriented database systems (ed. Zdonik, S. B. / Maier, D.)" ISBN 055860 -000-0; Morgan Kaufmann publishers.

No context found.

L.A. Rowe and M.R. Stonebraker, \The Postgres Data Model," in Proceedings of the International Conference on Very Large Databases, Brighton, 1987, pp. 83-96. 23

No context found.

L.A. Rowe and M.R. Stonebraker, \The Postgres Data Model," Proceedings of the Thirteen International Conference on Very Large Databases, Brighton, pp. 83-96, 1987.

No context found.

L. Rowe, M. Stonebraker, The POSTGRES Data Model, Proc. of the Intern. Conference on Very Large Data Bases, 83-96, (1987).

No context found.

L. Rowe, M. Stonebraker, The POSTGRES Data Model, Proceedings of the Intern. Conference on Very Large Data Bases (VLDB'97), 83-96 (1987).

No context found.

Lawrence A. Rowe and Michael R. Stonebraker. The POSTGRES Data Model. In Proceedings of the 13th International Conference on Very Large Databases, Brighton, England (VLDB '87), pages 83--96, September 1987.

No context found.

L. A. Rowe and M. R. Stonebraker. "The POSTGRES Data Model. " In P. Hammersley, editor, vldb, pp. 83--96, Brighton, England, September 1987.

No context found.

Lawrence A. Rowe and Michael R. Stonebraker. The POSTGRES data model. In Peter M. Stocker and William Kent, editors, Proceedings of the Thirteenth International Conference on Very Large Databases, Morgan Kaufmann Publishers Inc., 1987.

No context found.

L. Rowe and M. Stonebraker. "The POSTGRES Data Model." In Proceedings of VLDB Conference, Brighton, England, September 1987.

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