Overview of the Iris DBMS

Fishman, D.; Annevelink, J.; Chow, Ey-Chih; Conners, Terrance E.; Davis, James W.; Hasan, W.; Hoch, Charles G.; Kent, William; Leichner, S.; Lyngbæk, Peter; Mahbod, B.; Neimat, Marie-Anne; Risch, Tore; Shan, Ming-Chien; Wilkinson, W. Kevin

doi:10.1145/63320.66505

Cited by 77 publications

(9 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the second example we make use of a virtual function for a more complex join. 10 All employees that have the same manager as x are collected in the function colleagues, whose scope is limited by t h e let operation. If we a r e interested in all employees who have at least one colleague, the virtual function colleagues can be used in the subsequent selection: let colleagues = x : manager]: select y: manager(y) = manager(x)x 6 = y](adom (Empl)) in select x: colleagues(x) 6…”

Section: Semantics Of Expressionsmentioning

confidence: 99%

See 1 more Smart Citation

A Functional Object Database Language

Laasch

Scholl

1994

Database Programming Languages (DBPL-4)

View full text Add to dashboard Cite

The language BCOOL is formally de ned using a denotational semantics approach. BCOOL is a functional object database language with a very exible, yet strong and statically checked, type system. Its main source of exibility is its support for object evolution, that is, dynamic type changes of existing objects. Originally, B C O O L w as used as a formal basis for a more traditional (relational algebra-style) database language, COOL. In this paper, though, BCOOL is presented on its own. The purpose being to compare with other functional languages and discuss the virtues and limitations that BCOOL and these functional languages have w.r.t. each other in terms of (i) the above-mentioned exibility in the type system, which w e consider essential for objects and (ii) the orthogonality of the language.

show abstract

Section: Semantics Of Expressionsmentioning

confidence: 99%

“…The type inference rule means that e 1 :: 1 can be inferred under the assumption that f is a variable of type 2 10. See 21] for a discussion of di erent alternatives for joins: symmetric tuple/object generating asymmetric as functions.…”

mentioning

confidence: 99%

A Functional Object Database Language

Laasch

Scholl

1994

Database Programming Languages (DBPL-4)

View full text Add to dashboard Cite

show abstract

“…Prototype implementations of version management systems in ODBMS are described in [FISH89] and [KIMW88b] Cooperative transaction processing and versioning appear to be probable requirements for future CAD systems, office information systems, and sophisticated artificial intelligence systems.…”

Section: Support For Versioningmentioning

confidence: 99%

“…Some of these systems, while they do not incorporate all aspects of the object data model, as presented in section 5, do support many of the functions associated with object systems. Examples [FISH89] uses the ALLBASE relational DBMS as its storage manager.…”

Section: Review Of Odbmsmentioning

confidence: 99%

Object database management systems

Dabrowski¹,

Fong²,

Yang³

1990

View full text Add to dashboard Cite

Institute of Standards and Technology (NIST) (formerly National Bureau of Standards (NBS)) has a mission under Public Law 89-306 (Brooks Act) to promote the "economic and efficient purchase, lease, maintenance, operation, and utilization of automatic data processing equipment by federal departments and agencies." When a potentially valuable technique first appears, NCSL may be involved in research and evaluation. Later on, standardization of the results of such research, in cooperation with voluntary industry standards bodies, may best serve federal interests. Finally, NCSL helps federal agencies make practical use of existing standards and technology through consulting seirvices and the development of supporting guidelines and software. A new information management technology, called Object Database Management Systems (ODBMS) is rapidly emerging. A common definition of ODBMS is needed to avoid confusion among the users, vendors, and standards developers in the database community. The purpose of this report is to describe object concepts and identify a set of features associated with ODBMS. Certain commercial software products and companies are identified in this report for purposes of specific illustration. Such identification does not imply recommendation or endorsement by the National Institute of Standards and Technology, nor does it imply that the products identified are necessarily the best available for the purpose.

show abstract

“…Section 3). This language was inspired by some proposals made for query languages for the Entity Relationship model 8,11], as well as proposals to extend SQL to cope with features of other database models than the relational one 30,16]. Syntax and semantics of this language are de ned using an Extended Backus-Naur Form grammar.…”

Section: Introductionmentioning

confidence: 99%