| Richardson, J. E., M. J. Carey, and D. H. Schuh, "The Design of the E Programming Language", ACM Transactions on Programming Languages and Systems, Vol. 15, No. 3, July 1993. Also in [54]. |
....a salient point of this model that concurrency control is incorporated into data objects, as will be explained later. The description of the model in this section is rather conceptual and given mostly in Smalltalk terms. Examples of language constructs implementing such a model are found in, e.g. [Agra89, Rich89], both of which borrow and extend the object definition facility of C . 5.2.2. Object Model An object consists of five components; a unique name or identifier of the object, a set of attributes, a set of methods, a set of constraints, and a concurrency control mechanism. Attributes characterize ....
Richardson, J. E., M. J. Carey, and D. H. Schuh, "The Design of the E Programming Language," Computer Sciences Technical Report #791, Univ. of Wisconsin, Madison, February 1989.
....17 ### ###5 ah# =K#;Qffi m# ####HL, K#;Qae ## HL OE 7L ah9L)### ###9L f ### j ### =K#;Q# ae # # im i OE 2L m#j . ###5 ah## #ffi ae im ffi ) f =K#;Q i ### CK#,# #:L # CG j j ### =K#;Q# 9 ko ##ko9L i OE i # j # ae # #9L) # # # :Lffi JK# # )# #j . E[20][22] O [2] Avalon C [9]### #### =K#;Qae ## HL OE 7L ah .#)9L)### ###ae ffi # ae,#chim #ae,# # ######### ,#ae,# ae #ae,# # # #:L### f### ## f UW #j . E# 9M### f # j ##### ffi #j [20] dbclass person f Delta Delta Deltag; dbclass City : collection[person] City Seoul; ....
....CG j j ### =K#;Q# 9 ko ##ko9L i OE i # j # ae # #9L) # # # :Lffi JK# # )# #j . E[20] 22] O [2] Avalon C [9]### #### =K#;Qae ## HL OE 7L ah .#)9L)### ###ae ffi # ae,#chim #ae,# # ######### ,#ae,# ae #ae,# # # #:L### f### ## f UW #j . E# 9M### f # j ##### ffi #j [20]. dbclass person f Delta Delta Deltag; dbclass City : collection[person] City Seoul; person p1 = new(Seoul)person( Chough ) ffi.#### collection### , City 6# ## ae # # Seoul### # #j . ###, ###ae,# # OE #### ###afim ### ae # #### j i # OE #chim ae,##m# #) ....
[Article contains additional citation context not shown here]
Joel E. Richardson, Michael J. Carey, and Daniel T. Schuh. "The Design of the E Programming Language". Technical Report #824, Computer Science Department, University of Wisconsin-Madison, February 1989.
....can be accessed in the context of any single transaction is limited only by the size of virtual memory. The paper also presents the results of a detailed performance study, in which we use the OO7 benchmark [Carey93] to compare the performance of QuickStore with the latest implementation of E [Rich93], a persistent programming language developed at Wisconsin that is also based on C . The comparison between QuickStore and E is interesting because each of the systems takes a radically different approach toward implementing persistence. QuickStore employs a hardware faulting scheme that relies ....
....pointer fields of all transient and persistent objects that contain pointers to the fault block. Finally, we note that the effects of page replacement in the buffer pool and updates are also not considered in [Hoski93a] In [White92] the performance of several implementations of the E language [Rich93, Schuh90] and ObjectStore [Objec90, Lamb91] a commercial OODBMS, are compared. The results presented in [White92] were inconclusive, however, in providing a true comparison of software and hardware based schemes since the underlying storage managers used by the systems were different and because the ....
J. Richardson, M. Carey, and D. Schuh, "The Design of the E Programming Language", ACM Transactions on Programming Languages and Systems, Vol. 15, No. 3, July 1993.
....[19] O also shares the concerns of the persistent programming languages, such as [6, 16, 38, 40 42] persistence is a property of object instances and not types, and persistent objects are accessed and manipulated in much the same way as volatile objects. O is related to the language E [41, 42] in that O , like E, also uses the C object model and adds persistence to it. Vbase [7] and O2 [32] also seek to blend an object oriented data model with C. In this paper, we concentrate on the data modeling and the query processing aspects of O . We do not cover concurrency issues and some ....
....in a set need not be specified: userid users ; The set operations supported are assignment, union, difference, insertion, and deletion. Set elements are accessed by using the set iteration facility (discussed later) 2. 7 Related C based Approaches The database implementation language E [41, 42] also started with C and added persistence to it. In E, persistent objects must be of special types called db types. Objects of such types can be volatile or persistent. Persistent objects can be allocated statically by using the storage class persistent in object definitions or they can be ....
J. E. Richardson, M. J. Carey and D. H. Schuh, "The Design of the E Programming Language", Computer Sciences Tech. Rep. #824, Univ. Wisconsin, Madison, Feb. 1989.
....and compared in [6] Issues in integrating databases and programming languages have been discussed in [6, 10, 11, 26, 33, 38] In the remainder of this section, we limit our discussion to some other ongoing work on combining C and C with databases. Closely related to our work is the language E [26, 27], which also started with C and added persistence to it. However, persistent objects in E must be of special types called db types. Objects of such types can be volatile or persistent. Persistence orthogonality in E can thus be realized by programming exclusively in db types, but all ....
J. E. Richardson, M. J. Carey and D. H. Schuh, "The Design of the E Programming Language", Computer Sciences Tech. Rep. #824, Univ. Wisconsin, Madison, Feb. 1989.
.... to also include the specification of persistence within variable declarations, such as through the use of a special keyword (e.g. persistent) Many systems have a persistence mechanism that may be considered allocation based, including ObjectStore [Lamb et al. 91] the E programming language [Richardson et al. 89] and the O programming language used in the ODE database system [Agrawal et al. 89a] A point of interest in regard to allocation based persistence is that it is not possible for an object s level of persistence to change dynamically. To simulate change of persistence level, values can be copied ....
....is that it reduces the likelihood of dangling references occurring within persistent objects. A dangling reference occurs when an attribute refers to transient memory. Although many agree it s a powerful mechanism, reachability is often not employed due to a number of associated disadvantages [Richardson et al. 89, Cattell 94] Some of these are outlined below. The need for extra runtime information Supporting persistence by reachability usually requires extra information to be present at run time, in order to perform the reachability traversal to determine whether a particular object is persistent. ....
[Article contains additional citation context not shown here]
Richardson, J.E., Carey, M.J. & Schuh, D.T., "The Design of the E Programming Language" (1989) Computer Sciences Technical Report No.824, University of Wisconsin, Madison
....kind of spatial database systems. This type of database technology is needed to support applications such as Geographic Information System (GIS) This paper describes a data model and its query language for a prototype developed at the University of Waterloo. The prototype is implemented with E [20] and X Motif on a Sun workstation under Unix. The system, as well as its query language, are called QL G which stands for a query language for geometric databases. QL G consists of two main components: a user friendly graphical user interface, and a query processor. QL G, like most systems ....
Richardson, J., Carey, M.J. and DeWitt D.J., "The Design of the E Programming Language, " ACM TOPL, 1992.
....programming environments. However the only data type that may persist in such environments is the byte. The benefits of strong typing such as improved safety and data modelling power over the whole environment cannot be achieved. An example of such a system is the combination of the language E [RCS89] an extension of C , with the EXODUS Storage Manager [Car89] The Storage Manager provides storage objects which are uninterpreted byte sequences of virtually any size. The aim is to build and extend database systems by writing the database system code in E. E inherits from C the lack of ....
J. Richardson, M. Carey and D. Schuh "The Design of the E Programming Language" Computer Sciences Dept., University of Wisconsin Report 824 (1989).
....in a persistent state after it is created or updated. Geometric data involved in QL G are in general complex objects. To simplify the implementation, we chose an object oriented programming language that supports data persistence to build the prototype. In this case, the E programming language [24], which is an extension of C , is chosen to implement QL G. The E language requires the EXODUS storage manager which is an object storage system providing concurrency control and recovery. Other packages used include Bison [8] and Flex [21] for building the query processor, and X Motif for ....
Richardson, J., Carey, M.J. and DeWitt D.J., "The Design of the E Programming Language, " ACM TOPL, 1992.
....forms for entering bio diversity data and queries. This information is passed on to the Database Server which parses and processes the information. The server implements the OSHADHI object model and uses the EXODUS Storage Manager to store the database. It is written using the E language [Rich89], which is a database programming language supported by EXODUS. The EXODUS Storage Manager, which forms the lowest layer of OSHADHI, serves requests from the database server with regard to object management and transaction processing. The OSHADHI database includes the taxonomy details of various ....
Richardson, J.E., Carey, M.J., and Schuh, D., "The Design of the E Programming Language", Tech. Report, Computer Sciences Dept., Univ. of Wisconsin (Madison), February 1989.
No context found.
Richardson, J. E., M. J. Carey, and D. H. Schuh, "The Design of the E Programming Language", ACM Transactions on Programming Languages and Systems, Vol. 15, No. 3, July 1993. Also in [54].
No context found.
Joel E. Richardson, Michael J. Carey and Daniel T. Schuh, `The design of the E programming language', Technical Report, University of Wisconsin, 1989. To appear, TOPLAS.
No context found.
J. Richardson, M. Carey, and D. Schuh, "The Design of the E Programming Language", ACM Trans. on Prog. Lang. and Sys., Vol. 15, No. 3, July 1993.
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