L.J. Gallagher. Object SQL: Language Extensions for Object Data Management. In Proc. 1st International Conference on Information and Knowledge Management, pages 17--26, November 1992.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....in [29] TQL is based on the SQL paradigm. We adopt this paradigm for various reasons. Most importantly, SQL is accepted as the standard language in relational databases, and current work on SQL3 attempts to extend its syntax and its semantics to fulfill requirements of object oriented systems [12]. The semantics of TQL is defined in terms of the object calculus. In fact, there is a complete reduction from TQL to the object calculus. In addition, TQL extends the basic SQL structure by accepting path expressions (i.e. implicit joins [19] in the select, from, and where clauses. Object ....

L.J. Gallagher. Object SQL: Language Extensions for Object Data Management. In Proc. 1st International Conference on Information and Knowledge Management, pages 17--26, November 1992.

....execution. Current trends in database management systems (DBMS) include extensions to incorporate object modeling capabilities into deductive databases [4] or to incorporate triggers and constraints into object oriented DBMS (OODBMS) 16, 17] or to enhance SQL with object oriented capabilities [14]. A system, whose goal is specifically the integration of object oriented, deductive and active capabilities has been developed as part of the ESPRIT Project Idea [6, 7] In this work we shall describe the data model of Idea, called Chimera [9, 19, 8] and we shall give a semantics for it. We have ....

L.J. Gallagher. Object SQL: Language Extensions for Object Data Management. In Proceedings of the 1st International Conference on Information and Knowledge Management (CIKM), Baltimore, Maryland, November 1992.

.... has been chosen as a representative of modern database management systems (DBMS) These incorporate, for instance, objects modeling capabilities into deductive databases [5] triggers and constraints into object oriented DBMS (OODBMS) 19, 20] or enhance SQL with object oriented capabilities [16]. The next step of this research will be to precisely define which are the relations between Linear Logic and other formalisms developed to assign a semantics to transactions and updates, e.g. 6, 41, 28] See also the final section for a brief comparison between our approach and some of the ....

L.J. Gallagher. Object SQL: Language Extensions for Object Data Management. In Proceedings of the 1st International Conference on Information and Knowledge Management (CIKM), Baltimore, Maryland, November 1992.

....scheduling of transactions and method invocations [Senerchia, 1993] We are currently developing a transaction system for our prototype real time objectoriented database. A major focus of this effort is an extension of the standard SQL query language with capabilities to support objects [Gallagher, 1992] and real time properties [Wolfe Cingiser, 1992] as the interface to generate transactions. Many of the features of the RTC language constructs that we used to describe the index arbitrage example are supported in this real time SQL extension, such as explicit timing constraints. Once the SQL ....

Gallagher, L. (1992). Object SQL: Language extensions for object data management. Proceedings of International Society For Mini and Microcomputers, 4, 156-162.

....interesting proposals in this sense. In fact, it combines aspects of all the other proposals in the field, e.g. object modeling capabilities into deductive databases [5] triggers and constraints into object oriented DBMS (OODBMS) 20, 21] and query languages with object oriented capabilities [17]. Given the high complex structure of the considered data model, it would be desirable to have a clear and possible modular formalization of the meaning of all of its components. In fact, formal specifications are an indispensable support to the implementation, verification and analysis of a new ....

L.J. Gallagher. Object SQL: Language Extensions for Object Data Management. In Proceedings of the 1st International Conference on Information and Knowledge Management (CIKM), Baltimore, Maryland, November 1992.

....10. Finally, the query language whether used on an ad hoc basis, or embedded in application programs should not violate encapsulation. Data abstraction is one of the most important concepts in object oriented systems, therefore, it should be maintained [Bla91] 1.3. 2 Object Query Languages SQL3 [Gal92] which is under development as an international standard, is expected to incorporate numerous object oriented features. It will be a complete language for managing, creating and querying persistent objects. It will provide facilities for defining new abstract data types (ADT) creating new ....

....on the SQL select from where structure. We have decided to adopt this structure for various reasons. First of all, SQL is the standard language for relational systems. Second, current work on SQL3 attempts to extend its syntax and its semantics to fulfill requirements of objectoriented systems [Gal92] Finally, any syntax of a query statement must provide a way to specify the three basic components of the query block. Instead of designing a new structure to achieve the same result, we have adopted the one which is already successful in other systems. TQL extends the basic SQL structure by ....

[Article contains additional citation context not shown here]

L.J. Gallagher. Object SQL: Language Extensions for Object Data Management. In Proc. 1st International Conference on Information and Knowledge Management, pages 17--26, November 1992.

....that can then be optimized at multiple SQL servers and invoked as needed, thereby reducing both processing time and communications volume. Features of the SQL 92 standard are discussed in References [1] 2] and [15] Proposed features of the next SQL revision, often called SQL3, are discussed in [4] and [5] SQL is particularly appropriate for the definition and management of data that is structured into repeated occurrences having common data structure definitions. SQL provides a high level query and update language for set at a time retrieval and update operations, as well as required ....

Gallagher, Leonard. Object SQL: Language Extensions for Object Data Management, Proceedings of the First International Conference on Information and Knowledge Management (CIKM), Baltimore, MD, 9-12 November 1992, International Society of Mini and Micrcomputers (ISMM), pages 17-26.

....in [29] TQL is based on the SQL paradigm. We adopt this paradigm for various reasons. Most importantly, SQL is accepted as the standard language in relational databases, and current work on SQL3 attempts to extend its syntax and its semantics to fulfill requirements of object oriented systems [12]. The semantics of TQL is defined in terms of the object calculus. In fact, there is a complete reduction from TQL to the object calculus. In addition, TQL extends the basic SQL structure by accepting path expressions (i.e. implicit joins [19] in the select, from, and where clauses. Object ....

L.J. Gallagher. Object SQL: Language Extensions for Object Data Management. In Proc. 1st International Conference on Information and Knowledge Management, pages 17--26, November 1992.

....is no universally accepted object query language which is not surprising since there is no accepted object model either. Our approach in designing an extensible query model gives us an advantage by ensuring that our model will be able to meet future information processing requirements. SQL3 [Gal92] is expected to incorporate numerous features for an object query language. It is intended to be a complete language for managing, creating and querying persistent objects. It provides facilities for defining new abstract data types (ADT) creating new functions and accessing objects. Moreover, ....

....on the SQL select from where structure. We have decided to adopt this structure for various reasons. First of all, SQL is the standard language for relational systems. Second, current work on SQL3 attempts to extend its syntax and its semantics to fulfill requirements of object oriented systems [Gal92] Finally, any syntax of a query statement must provide a way to specify the three basic components of the query block. Instead of designing a new structure to achieve the same result, we have adopted the one which is already successful in other systems. TQL extends the basic SQL structure by ....

[Article contains additional citation context not shown here]

L.J. Gallagher. Object SQL: Language Extensions for Object Data Management. In Proc. 1st International Conference on Information and Knowledge Management, pages 17--26, November 1992.

....the problem of formalizing a query model in an object oriented environment. These have led to the development of design frameworks for object algebras [YO91] object calculi [AB93] and query languages [Bla91, OSP94] Furthermore, some work is ongoing to extend SQL with object oriented features [Gal92] Straube and Ozsu [S O90] have investigated query processing issues in the domain of object oriented databases. They specify both an object algebra and calculus definition, and the two are linked with a calculus to algebra translation. However, the reduction is only partial and the algebra ....

....PL OS93] TQL is based on the SQL paradigm. We adopt this paradigm for various reasons. Most importantly, SQL is accepted as a standard query language in relational databases, and current work on SQL3 attempts to extend its syntax and semantics to fulfill requirements of object oriented systems [Gal92] The semantics of TQL is defined in terms of the object calculus. In fact, there is a complete reduction from TQL to the object calculus. In addition, TQL accepts path expressions (implicit joins [KBC 89] in the select, from and where clauses. Object equality is defined on the primitive ....

[Article contains additional citation context not shown here]

L.J. Gallagher. Object SQL: Language Extensions for Object Data Management. In Proc. of the 1st International Conference on Information and Knowledge Management, pages 17--26, November 1992.

....a deductive query language. This permits the programmer to take advantage of the features of both object oriented database languages and deductive database languages in developing applications. The Coral query language is significantly more expressive than the objectoriented extensions of SQL ([8, 6], for instance) A non operational semantics is however maintained, and this makes Coral more amenable to automatic query optimization than imperative languages for object oriented databases ( 7, 1] for instance) that have similar expressive power. ffl To cleanly integrate a declarative ....

....object oriented data models and declarative query languages. Some of the important aspects of our design are: ffl Coral uses the type system of an existing object oriented programming language (i.e. C ) as an object data model rather than inventing yet another object data model (e.g. [28, 8, 13, 9, 10, 17, 2]) This approach benefits from the support for data abstraction, inheritance, polymorphism and parametrized types already available in C . Other query languages that use the C type system include CQL [6] ZQL[C ] 3] and ObjectStore [20] ffl The Coral declarative query language supports ....

[Article contains additional citation context not shown here]

L. J. Gallagher. Object SQL: Language extensions for object data management. In Proceedings of the ISMM First International Conference on Information and Knowledge Management, pages 17--26, Baltimore, Maryland, Nov. 1992.

....query languages with object oriented features in the forum of the international data speak of SQL. The broad acceptance of SQL as a standard query language in relational databases, together with the current efforts on SQL3 to extend the syntax and semantics with object oriented features [Gal92] are the main motivations for our SQL basis. The semantics of TQL is defined in terms of the object calculus. In fact, there is a complete reduction from TQL to the object calculus [Lip93] In addition, TQL accepts path expressions (implicit joins [KBC 89] in the select, from, and where ....

L.J. Gallagher. Object SQL: Language Extensions for Object Data Management. In Proc. 1st International Conference on Information and Knowledge Management, pages 17--26, November 1992.

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