ATKINSON,M.AND MORRISON, R. 1995. Orthogonally persistent object systems. VLDBJ. 4, 3, 319--401. ATKINSON,M.P.AND BUNEMAN, O. P. 1987. Types and persistence in database programming languages.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....method returns itself (self local reference) As described above, when this reference is to be returned by MOM to a remote site, MOM transfers the whole object that is referenced, in this case the object itself. 2.2. Persistence by Encapsulation In general, we adopt the approach taken in [3] and employ persistence independence meaning that the semantics of an object is not changed by its longevity, and persistence orthogonality meaning that any object of any type (including a mobile object) can be made persistent. Our design of persistence for mobile objects is highly ....

M. P. Atkinson and R. Morrison. Orthogonally persistent object systems. VLDB Journal, 4(3), 1995.

....persistence (CMP) In the application server area, standards that promote transparent persistence have emerged. A good example is the container managed persistence promoted by EJB [22] but more complex models (e.g. JDO [23] have also been proposed. Their bene ts have been analyzed elsewhere [7, 6]. A spontaneous container could be used similarly for securing the state of any Java based services. Following this idea, we have developed a solution adapted to the dynamic character of a spontaneous container. It consists of an objectrelational mapper (ORM) and relies on capturing object eld ....

M. P. Atkinson and R. Morrison. Orthogonally Persistent Object Systems. VLDB Journal, 4(3):319-401, 1995.

....and persistence In the application server area, standards that promote transparent persistence have emerged. A good example is the container managed persistence promoted by EJB [Mic01a] but more complex models (e.g. JDO [Mic01b] have been proposed. Their bene ts have been analyzed elsewhere [AM95, ADJ 96] For securing the state of Jini services, a similar approach would be bene cial. Following this idea, we have developed a solution adapted to the dynamic character of Jini. It consists of an object relational mapper (ORM) and relies on capturing object eld changes at run time using ....

M. P. Atkinson and R. Morrison. Orthogonally Persistent Object Systems. VLDB Journal, 4(3):319{ 401, 1995.

....[3] These problems are manifested by Java OQL [15] which requires run time reflection (or dynamic compilation) as an implementation technique. The type of reflective techniques required for a type safe implementation of Java OQL have been developed for other persistent object systems ( 16] [12]) But these techniques are by no means trivial, and go beyond the bounds of the usual static type checking techniques. MyT queries can be statically type checked, as one would naturally expect. The core of the query capabilities is the predefined parametric class Query[T] equipped with an ....

Atkinson, M., Morrison, R.: Orthogonally Persistent Object Systems, VLDB Journal 4 (1995) 319-401. 216

.... web services may exist, depending for example on the particular requested implementation for the persistent data (e.g. relational databases, XML files) 53 Our way to create and manage persistent data is very similar in spirit with the approaches proposed for persistent programming languages [AM95] However, the novel Web services context imposes the reconsideration of a certain number of issues. For example, unlike most traditional persistent programming languages, we do not recommend for XL the concept of persistence by reachability. In other words, the newly created data persists even ....

M. P. Atkinson and R. Morrison. Orthogonally persistent object systems. The VLDB Journal, 4(3), 1995.

....or deletion of a persistent object) are handled by the underlying system and do not correspond to the execution of a user statement. In our proposal a trigger monitor both the persistent and the non persistent instances of a class. Note that is in accordance with the orthogonal persistence [ATK 95] principle on which most Java based databases are based. 3.3. Trigger Inheritance and Overriding In adapting the SQL:1999 trigger definition language to an object oriented context, however, the main issues to be investigated concern trigger inheritance and overriding. Such issues have neither ....

ATKINSONS M., MORRISON R., "Orthogonally Persistent Object Systems", VLDB Journal, vol. 4, 1995, p. 319-401.

....term for mechanisms that allow application data from a program s execution space to somehow survive the execution of the program, so that in a later execution it can be used again. There are many possible schemes for supporting persistence. For a complete survey, the reader should refer to [1]. The most sophisticated and desired form of persistence is orthogonal persistence [2] It is the provision of persistence for all data irrespective of their type. In a programming language providing orthogonal persistence, persistent data is created and used in the same way as non persistent ....

Atkinson, M.P.; Morrison, R.: "Orthogonally Persistent Object Systems". VLDB Journal 4(3), pp.319--401, 1995.

....persistence [3, 4] relies on saving values of data from a program execution space so that they can be used in a later execution: that is the values persist from one execution to another. There are many possible schemes for supporting persistence; for a complete survey, the reader is referred to [5]. In our opinion fault tolerance and persistence are quite distinct program properties and there are important differences in the way data saving is used in these two areas. Persistence relies on saving data values to allow them to be used in a later execution. In fault tolerant systems the state ....

Atkinson, M. P.; Morrison, R.: "Orthogonally Persistent Object Systems". VLDB Journal 4(3), pp. 319 -- 401, 1995.

....stack, be saved prior to a move so that it can be restored once the agent has moved to its new location. The standard term describing this process is checkpointing [23] Over the last few years, the more general concept of orthogonal persistence has also been developed by the research community [2]. The goal of orthogonal persistence research is to define language independent principles and language specific mechanisms by which persistence can be made available for all data, irrespective of type. Ideally, the approach would not require any special work by the programmer (e.g. ....

Atkinson, M. P., & Morrison, R. (1995). Orthogonally persistent object systems. VLDB Journal, 4(3), 319-401.

....e.g. Java, Smalltalk, or C . In contrast, relational database systems rely on declarative access languages like SQL and the relational data model. Thus, the usage of relational database technology implies a switch between different data models and language paradigms in the application program [4, 19]. The application programmer is forced to deal with both. ffl update notification: current DBMS enforce the ACID properties of transactions [10] They strive to give each transaction user the illusion of a single user system opposing to groupware systems which strive to make each user s actions ....

M. Atkinson and R. Morrison. Orthogonally persistent object systems. VLDB Journal, 4(3):319--401, 1995.

....which explicit storage management is performed. Thus it might seem that automatic storage management has little role to play. However, the inherent advantages of these more advanced languages (in particular: correctness, maintainability, understandability) are a strong incentive for their adoption [AM95]. Further, systems that seek to provide automatic performance tuning may take advantage of algorithms with known performance costs. We have built a demonstration system, and present initial measurements of its behaviour, with particular emphasis on the utility of the tuning controls. Our interest ....

Atkinson, M.P. & Morrison, R. "Orthogonally Persistent Object Systems". VLDB Journal 4, 3 (1995) pp 319-401.

....model like C or Smalltalk. In contrast, relational database systems rely on declarative access languages like SQL and the relational data model. Thus, the usage of relational database technology implies a switch between different data models and language paradigms in the application program [AM95, SZ87] The application programmer is forced to deal with both. # update notification: current DBMS enforce the ACID properties of transactions [Gra81] They strive to give each transaction user the illusion of a single user system which opposes the needs of workgroup applications. Instead of ....

M.P. Atkinson and R. Morrison. Orthogonally persistent object systems. VLDB Journal, 4(3):319--401, 1995.

....an intrinsic attribute of an object, supported by the infrastructure within which the object operates [1] That is, the persistence of an object should be orthogonal to use, type and identification of the object. 5 Orthogonal Persistence The three basic principles behind orthogonal persistence [7] are that: all objects may (persist) exist for as long, or as short, a period as is required, all objects are manipulated in the same manner, regardless of their longevity, and . the identification of persistent objects is not linked to the type system. All objects have the right to the ....

M. Atkinson.and.R. Morrison, "Orthogonally Persistent Object Systems", The VLDB Journal, 4(3), pp. 319-401, 1995.

....solutions. These solutions are much more comprehensive and powerful than object serialization. This section should not be read as a comparison of object serialization with these other technologies. 13.1 Orthogonal Persistence An object oriented orthogonally persistent programming language [AM95] seamlessly integrates the language with the technology for saving and restoring objects and their code to and from stable storage. Such languages are referred to as orthogonally persistent as any object, regardless of type, may be made persistent; the issues of typing and persistence are ....

M. P. Atkinson and R. Morrison. Orthogonally persistent object systems. VLDB Journal, 4(3):319--401, 1995.

....the persistent environment which provides editors, window managers, compilers etc. Unlike its predecessor, PS algol [43] which took the approach of extending an existing programming language, S algol [44] with persistence, Napier88 was designed as an integrated persistent programming system [45]. As such some of the decisions as to what is built into the language and what is supported by the environment are somewhat arbitrary and would justify re evaluation in future 2 designs. For example, bulk types and concurrency control are supported by values and procedures in the environment ....

Atkinson MP, Morrison R. Orthogonally Persistent Object Systems. VLDB Journal 1995; 4,3:319-401

....descriptive evolution models the same knowledge in a different manner. Changing the schemata of a database while maintaining the consistency of the data and programs belonging to them with the semantics of change has proved to be a difficult problem [Zdo86, Cla92, MCC 93, Odb94] As explained in [AM95], database programming languages have unified data models and type systems and some approximate equivalences can be recognised, as shown in Figure 1.1 below. Databases Programming Languages data model type system schema type expression database variable database extent value Figure 1.1 : ....

Atkinson, M.P. & Morrison, R. "Orthogonally Persistent Object Systems". VLDB Journal 4, 3 (1995) pp 319-401.

....class but 12 this is likely to add a slew of other problems related to the use of multiple inheritance. Also, this approach does not work for builtin types because their definitions cannot be changed easily in most languages. Unlike class based persistence, orthogonal persistence [ABC 83a, AM95] decouples the lifetime of an object from its type. In other words, persistence is viewed as a storage class 2 rather than as a property of the object type. The name derives from the requirement that the type of an object must be independent of (that is, orthogonal to) its storage class. In ....

....data formats or the code that manipulates them, it allows swizzled and unswizzled objects to be used freely in the same programs, with only a few restrictions on how they may interact. As discussed in Chapter 2, we use pointer swizzling at page fault time to implement orthogonal persistence [AM95] The orthogonal persistence model allows both transient and persistent objects to be treated in exactly the same way. This allows existing code, typically object code libraries, to be linked with an application without requiring any recompilation, as long as these libraries do not need to ....

[Article contains additional citation context not shown here]

Malcolm P. Atkinson and Ron Morrison. Orthogonally Persistent Object Systems. VLDB Journal, 4(3), 1995. 193

No context found.

M.P. Atkinson and R. Morrison. Orthogonally Persistent Object Systems, VLDB Journal, 4(3), pp319-401, 1995.

No context found.

M.P. Atkinson and R. Morrison. Orthogonally Persistent Object Systems, VLDB Journal, 4(3), pp319-401, 1995.

No context found.

ATKINSON,M.AND MORRISON, R. 1995. Orthogonally persistent object systems. VLDBJ. 4, 3, 319--401. ATKINSON,M.P.AND BUNEMAN, O. P. 1987. Types and persistence in database programming languages.

No context found.

Mike P. Atkinson and Ron Morrison. Orthogonally persistent object systems. VLDB Journal, 4(3):319--401, 1995.

No context found.

M. P. Atkinson and R. Morrison. Orthogonally persistent object systems. VLDB Journal, 4(3):319--401, 1995.

No context found.

M. Atkinson, R. Morrison. Orthogonally Persistent Object Systems. The VLDB Journal, 4(3), 1995, pp.319-401.

No context found.

M. P. Atkinson and R. Morrison, "Orthogonally persistent object systems", VLDB Journal, vol. 4, no. 3, 1995.

No context found.

Atkinson, Morrison 95: Atkinson, M. and Morrison, R. "Orthogonally Persistent Object Systems". VLDB Journal, 4(3), 1995.

First 50 documents

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