P. Buneman and M. Atkinson, Inheritance and Persistence in Database Programming Languages, Proc. ACM SIGMOD Conf. 15,2 (May 1986), 4-15.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....in traditional programming languages. In many languages, such as Algol and Pascal [JeW75] they are a kind of stepchild which is explicitly disavowed by the parent language In others, only inherently sequential stream I O is supported. None, with the possible exception of persistent Pascal [BuA86, CAD87], employ a computational model in which the process is coequal with a permanent database from which specific data items are directly accessible. ADAMS was created in response to these kinds of perceived deficiencies. This report represents the combined design efforts of its authors over a three ....

P. Buneman and M. Atkinson, Inheritance and Persistence in Database Programming Languages, Proc. ACM SIGMOD Conf. 15,2 (May 1986), 4-15.

....a list in volatile store . proot = proot add(p) vroot = vroot add(v) 2. 5 Clusters of Persistent Objects All persistent objects of the same type are grouped together into a cluster; the name of a cluster is the same as that of the corresponding type, that is, clusters are type extents [15]. Before creating a persistent object, the corresponding cluster must exist; it is created by invoking the create macro 6 in this program or in another program: 6. Eventually we intend to extend the create macro to allow the programmer to give additional information to ....

P. Buneman and M. Atkinson, "Inheritance and Persistence in Database Programming Languages", Proc. ACMSIGMOD 1986 Int'l Conf. on Management of Data, Washington D.C., May 1986, 4-15.

....objects of the same type. Initially, we decided that there would be a one to one correspondence between cluster names and the corresponding type names. Whenever a persistent object of a type was created, it was automatically put in the corresponding cluster. Thus, our clusters were type extents [12]. This strategy preserved the inheritance relationship between the different objects in the persistent store, and worked nicely with our iteration facilities (discussed in the next section) allowing us to iterate over a cluster, or over a cluster and clusters derived from it 3 . Before ....

P. Buneman and M. Atkinson, "Inheritance and Persistence in Database Programming Languages", Proc. ACM-SIGMOD 1986 Int'l Conf. on Management of Data, Washington D.C., May 1986, 4-15.

....such as all files unused since 1 January 1987, that I choose to name be regarded as a single entity and be implementable as such . These are not unsurmountable issues; but clearly they can be messy. Third, as we develop computer languages that are capable of handling persistent objects, e.g. [BuA86], we must be able to create and name persistent types, which are not traditional entities and need not be singular. In ADAMS, the Advanced DAta Management System being developed at the University of Virginia [PSF87] we resolve a number of these issues by regarding as names all noun like words ....

P. Buneman and M. Atkinson, Inheritance and Persistence in Database Programming Languages, Proc. ACM SIGMOD Conf. 15,2 (May 1986), 4-15.

....in traditional programming languages. In many languages, such as Algol and Pascal [JeW75] they are a kind of stepchild which is explicitly disavowed by the parent language In others, only inherently sequential stream I O is supported. None, with the possible exception of persistent Pascal [BuA86, CAD87], employ a computational model in which the process is coequal with a permanent database from which specific data items are directly accessible. ADAMS was created in response to these kinds of perceived deficiencies. This report represents the combined design efforts of its authors over a three ....

P. Buneman and M. Atkinson, Inheritance and Persistence in Database Programming Languages, Proc. ACM SIGMOD Conf. 15,2 (May 1986), 4-15.

....terms, the database technology can be extended to accommodate new concepts and new requirements from new applications in three ways. One is to start from a programming language and incorporate database notions such as persistence, concurrency and recovery to suit the needs of database applications [Atkinson83, 84, 87, Buneman86, Cockshott84, Copeland84 ]. In this instance, the problem of impedance mismatch (bulk data types versus individualized types, hidden iteration versus explicit loop control, etc. Copeland84] must be addressed. A second approach is to start from a database system and build into it a rich type system and other useful ....

Buneman, O. P. and Atkinson, M. P., "Inheritance and Persistence in Database Programming Languages," Proceedings of the ACM-SIGMOD International Conference on the Management of Data, 1986.

....a large virtual persistent memory which processes can use to store and access items of data in much the same way that programming languages now allow the storage and access of data in volatile memory. Approaches to accomplish this kind of data management have been proposed in Persistent Algol [BuA86] and ODE [AgG89] Three differences which characterize the ADAMS approach are that, 1) the virtual persistent memory can be shared between distinct users if desired; 2) it is not language specific the programmer may code in any of the standard programming languages, such as C, Pascal, Ada, or ....

P. Buneman and M. Atkinson, Inheritance and Persistence in Database Programming Languages, Proc. ACM SIGMOD Conf. 15, 2 (May 1986), 4-15.

....any) The first defines (or names) an abstract class of things. The second names a specific instance (thing or object) within a class. Notice that the is a construct used to define new classes is a general class definition operator. It is not a specific inheritance operator as in [ACO85] or [BuA86] even though the defined class does inherit the properties of class . The class name or instance name , together with its corresponding definition is automatically entered into the users local dictionary. It is now part of the user s own database language. The name and its definition may be ....

P. Buneman and M. Atkinson, Inheritance and Persistence in Database Programming Languages, Proc. ACM SIGMOD Conf. 15,2 (May 1986), 4-15.

....feasible to support this feature by supersetting the query language, and this will certainly be the method of choice for SQL vendors. 4.3. Object Management If I hear the phrase everything is an object once more, I think I will scream. Peter Buneman expressed this frustration most concisely in [BUNE86]: Object oriented is a semantically overloaded term . Moreover, in a panel discussion on Object Oriented Data Bases (OODBs) at VLDB 87, six panelists managed to disagree completely on exactly what an OODB might be. In any case, there are a class of applications which must manage data that does ....

Buneman, P. and Atkinson, M., "Inheritance and Persistence in Database Programming Languages," Proc. 1986 ACM-SIGMOD Conference on Management of Data, Washington, D.C., May 1986.

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