Lyngbaek P. OSQL: A language for object databases. Technical Report, HP Labs, HPL-DTD-91-4, 1991.  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... database facilities, such as a storage manager, a recovery manager, a transaction manager, a disk backup manager, and a query processor for an object oriented (OO) query language, AMOSQL [5] AMOSQL is similar to the OO parts of SQL:99 [6] and based on the functional data model DAPLEX [7] and OSQL [8]. Each mediator server appears as a virtual OO database layer having OO data abstractions and query language. OO views provide transparent access to the data sources from clients and other mediator servers. Conflicts and overlaps between similar real world entities being modelled differently in ....

....AMOS II is designed for multi layered distribution of mediator servers where distributed query optimization [15] allows queries to be passed through many layers of mediators without any performance degradation. The AMOSQL query language has it roots in the functional query languages OSQL [8] and DAPLEX [7] with extensions of mediation primitives [9,10] multi directional foreign functions [14] late binding [16] active rules [17] etc. AMOSQL is relationally complete. Queries are specified using the select from where construct as in SQL. Due to its declarative nature, queries ....

Lyngbaek P. OSQL: A language for object databases. Technical Report, HP Labs, HPL-DTD-91-4, 1991.

.... databases [14] as opposed to just a vehicle for optimisation as in [30,19] or a notation for studying the theoretical foundation of query languages as in [7,17] The design criteria adopted are thoroughly discussed in [15] A comparison of object comprehensions with ONTOS SQL [29] OSQL [24], O 2 SQL [3] ORION [21] EXCESS [8] OQL[C ] 6] CQL [16] and XSQL [20] can be found in [12] 3.2 Object Comprehensions Q0. Return names of staff earning less than 20000. set[ s StaffMembers; s.salary 20000 s.name ] 5 An example of an object comprehension query is given above. ....

....specification of the resultant collection kind significantly simplifies the provision of algebraic support. OQL also allows such specification but with full type information. 3. 3 Expressive Power Object comprehensions are powerful because queries that can be expressed in ONTOS SQL [29] OSQL [24], O 2 SQL [3] and ORION [21] over the reference data model can also be expressed in object comprehensions. Translation rules from these query languages to object comprehensions can be found in [10] and those for ONTOS SQL are presented in [11] 3.4 Transforming Object Comprehensions It is ....

P. Lyngbaek. OSQL: A Language for Object Databases. Technical Report HPL-DTD-91-4, Hewlett-Packard Company, U.S.A., January 1991.

....in the paper is based on an initial implementation of a system called FEAMOS, which is an integration of a main memory OR DBMS, AMOS [4] with a FEA program, TRINITAS [5] AMOSQL, the query language of AMOS, is used to represent and manage the FEA domain model. AMOSQL is a derivative of OSQL [6] but is also influenced by SQL3 [7] TRINITAS, representing the state of the art within the field of FEA software, completely integrates the entire analysis process and is completely controlled through a graphical user interface. A typical TRINITAS session includes a generation of a finite element ....

....of the WS IRiS DBMS [21] WS IRiS is further a derivative of Iris [28] AMOS is a main memory database, i.e. it assumes that the entire database is contained in main memory and uses disk for backup only. It includes an object oriented extensible query language, AMOSQL, a derivative of OSQL [6], that is used to model and interface the database. AMOSQL is a functional language, originating from DAPLEX [29] and is also influenced by SQL3 [7] The data model consists of the basic constructs objects, types, and functions. The AMOSQL language is also extensible by calling external ....

Lyngbaek, P.: OSQL: A Language for Object Databases. HPL-DTD-91-4, Hewlett-Packard Company, January 1991.

....collection, a query language should be able to express dependency between generators. Generally speaking, in the absence of dependent generators, the fact that an object is an element of a nested collection has to be re established resulting in more verbose queries, for example, see OSQL [Lyn91] So far, there has been no convincing argument from the modelling perspective about restricting a query language to return only existing objects. Here a query language is required to allow new objects to be created in a query. It is not required that the corresponding classes are created along ....

....in discussing persistence meaning that a query language can work on both persistent as well as transient data. 3.4 An Evaluation of Existing Query Languages In this section four well known query languages are evaluated using the proposed requirements. They are the IRIS [LK86, Bee88, FAC 89, Lyn91] ORION[Kim90] ONTOS [Ont91a, Ont91b, Ont91c] and O 2 [Alt89, BDK92] query languages. These query languages are chosen as representative languages mainly because they are well reported and the most referenced in the literature. The result of the evaluation is summarised in Table 3.1 to Table ....

P. Lyngbaek. OSQL: A Language for Object Databases. Technical Report HPL-DTD-91-4, Hewlett-Packard Company, U.S.A., January 1991.

....is further a derivative of Iris (Fishman et al. 1989) AMOS is a main memory DBMS, i.e. it assumes that the entire database is contained in main memory. It includes the AMOSQLOR (i.e. OO and extensible) query language that is used to model and interface the database. AMOSQL is a derivative of OSQL (Lyngbaek et al. 1991). Furthermore, AMOSQL is a functional language, originating from DAPLEX (Shipman 1981) AMOS provides DBMS facilities including a local database, a data dictionary, a query processor, transaction processing, and remote access to data sources. It conforms to the mediator approach (Risch and ....

Lyngbaek, P., et al. 1991, OSQL: a language for object databases. Technical Report HPL-DTD-91-4, Hewlett-Packard Company.

....to avoid data shipping to the client. For this modern Object Relational DBMS therefore provide User Defined Functions (UDFs) 20] View in an object oriented data model can be represented as functions (or methods) defined using queries containing operators from the domain, e.g. for matrix algebra [23]. Such derived functions expressed by side effect free queries have a high abstraction level which is problem oriented and reusable. Query optimization techniques can be used to optimize such function definitions. To represent the model, an object relational DBMS with extensible storage ....

....those papers address late binding, multi methods, or multidirectional functions. We will show the benefits of having these features when modeling complex applications. OODBMSs have been the subject of extensive research during the last decade, e.g. 3] 4] 5] 34] Several OO query languages [9] 24][23] have been proposed. However, to the best of our knowledge processing queries with multi directional functions in OODBMSs has not yet been addressed. Multi methods require generalized type resolution methods compared to the type resolution of pure object oriented methods [1] 2] In the database ....

Lyngbaek, P.: OSQL: A Language for Object Databases. HPL-DTD-91-4, HP, Jan 1991.

....[3] or attach more than one meaning to a name appearing in a program [8] In this paper we are only concerned with the overloading of function names. If a name is overloaded in a subtype supertype relation there is an overriding of that name in the subtype. The following definitions in OSQL [6] define three functions with the same name but with different implementations. create function income(person p) integer j as stored; create function income(student s) integer j as select 0; create function income(Supervisor s) integer as select times(2,maxsal) for each integer maxsal, ....

Lyngbaek, P., "OSQL: A Language for Object Databases", Technical Report HPL-DTD-91-4, Hewlett-Packard Company, 1991.

.... functions, defined as queries, correspond to views in the relational model that are parameterized, and Foreign functions are defined using an external programming language [11] Our model extends the Iris data model with rules [19] 15] AMOS has a query language, AMOSQL, a deviate of OSQL [12]. In the AMOS data model the types are organized in a hierarchy where subtypes inherit all of its properties from their supertypes. In a subtype it is possible to redefine inherited properties and to add properties. We denote t i subtype of t j as t i t j . 2. By regular call we mean ....

P. Lyngbaek, "OSQL: A Language for Object Databases", Technical Report HPL-DTD-91-4, HewlettPackard Company, 1991.

....data model and in the query language. Subsequent sections consider valid and transaction time. 4.2 User defined Time User defined time is supported by most commercial relational DBMSs as another domain that can be associated with attributes. Hewlett Packard s object oriented query language OSQL [141] and UniSQL [109] continue in the SQL tradition by including Date, Time, and Timestamp types. Overmyer proposed making time an abstract data type, with its own set of operations [153] Many of the object oriented query languages (e.g. Postgres [205] and ZQL[27] can support user defined time in ....

Lyngbaek, P. "OSQL: A Language for Object Databases," Technical Report HPL-DTD91 -4, Hewlett-Packard Laboratories, Palo Alto, CA, January 1991.

....rules and contexts. 3 Rules and Contexts in the AMOS Active DBMS The active rules have been introduced into AMOS[5] 13] an Object Relational DBMS. The data model of AMOS is based on the functional data model of Daplex[14] and Iris[6] AMOSQL, the query language of AMOS, is a derivative of OSQL[11]. The data model of AMOS is based on objects, types, functions, and rules. Everything in the data model is an object, including types, functions, and rules[3] All objects are classified as belonging to one or several types, i.e. classes. Functions can be stored, derived, or foreign. Stored ....

....Object Ori ented system and to base tables in a relational system, derived functions correspond to methods and relational views, and foreign functions are functions written in some procedural language 1 . Database procedures are defined as functions that have side effects. AMOSQL extends OSQL[11] with active rules, a richer type system, and multidatabase functionality. 3.1 Contexts When rules are activated in AMOS, they are always associated with rule contexts. Contexts are first class objects and are created by the statement: create context context name where the context name is a ....

Lyngbaek P., OSQL: A Language for Object Databases, tech. rep. HPL-DTD-91-4, Hewlett-Packard Company, Jan. 1991

....type resolution and invertibility in a basic object oriented data model is presented. A basic object oriented model uses message passing as function invocation. The data model presented is strongly influenced by the functional data model DAPLEX [50] and by the Iris [28] data model with the OSQL [38] query language. OSQL (Object SQL developed at HP Lab) is an object oriented extension of SQL. The data model includes a query language AMOSQL.v0 1 [34] which is an extension of OSQL with rules [46] 51] This basic model will later in this thesis be used as platform for describing our approach ....

P. Lyngbaek, "OSQL: A Language for Object Databases", Technical Report HPL-DTD-91-4, Hewlett-Packard Company, 1991.

....the use of a neutral file format for exchange of data supported by each program. There are also more high level and direct methods for exchange of data between programs and between programs and databases. For example, there are query languages, such as SQL, ANSI [27] and OSQL, Lyngbaek [28], for communication with databases. Further, Part 22 of ISO 10303 is being defined, which should specify an application programming interface, called SDAI STEP Data Access Interface. Also the standardisation work within the Object Management Group, OMG [29] aims at facilitating the exchange of ....

Peter Lyngbaek, OSQL: A Language for Object Databases. Tech. Rept. HPL-DTD-91-4, Hewlett-Packard Company, January, 1991.

.... t developp a partir de la version WS Iris m moire principale de IRIS[FA 89] L element central d AMOS est AMOSQL, un language de requ tes objet relationnel qui offre une interface de requ tes declarative permettant de d finir, charger et manipuler la base de donn es. AMOSQL est d riv de OSQL[Lyn91] qui est un langage fonctionnel, ayant ces racines dans DAPLEX[Shi81] Le language de requ te AMOSQL est en plus influenc par les efforts de standarisation comme SQL3[Mel95] et OQL[Cat94] Comme dans OSQL, les requ tes AMOSQL sont compil es des plans d ex cution dans un langage logique OO ....

....manager. A central component of AMOS is an object relational query language, AMOSQL, with object oriented abstractions and declarative queries. The data model of AMOS and AMOSQL is strongly influenced by the functional data model OODAPLEX[Day89] and by the data model of Iris[FA 89] and OSQL[Lyn91]. The Iris data model has three basic constructs; objects, types and functions. The data model of AMOS extends that of Iris by introducing rules. Rules monitor changes to functions and changes to functions can trigger rules. Functions in AMOS can be stored, derived or foreign. Stored functions ....

[Article contains additional citation context not shown here]

Lyngbaek P.: OSQL: A Language for Object Databases, HPL-DTD-914, Hewlett-Packard Company, January 1991.

No context found.

P.Lyngbaek et al: `OSQL: A Language for Object Databases', Technical Report, HP Labs., HPL-DTD-91-4, January 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