IMS/XRF: Planning Guide, IBM, GC24-3151, IBM, White Plains, NY. 1987. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Types and Polymorphism in Persistent Programming Systems - Connor (1990) (16 citations) (Correct)
....in some database systems by restricting updates on view relations. Although this restriction is normally due to conceptual and implementation problems, rather than being a deliberate feature of a database system design, it may be used to some effect for this purpose. Some systems, for example IMS [IBM78], go further than this, and the database programmer can allow or disallow insertions, deletions, or modifications of data in view relations. This allows a fine grain of control for data protection purposes. There are a number of problems associated with view relations. Often a new relation is ....
IMS/VS Publications IBM, White Plains, N.Y. ( 1978 )
Models for Persistence in Lazy Functional Programming Systems - McNally (1993) (96 citations) (Correct)
....need only consider the mapping between the real world and the persistent programming language using a single computational model (Figure 1.3) Persistent Programming Language Real World Figure 1.3 A single mapping in a persistent system Secondly, there is a reduction in code size. One experiment [IBM78] found that 30 of the total code in a typical database application deals with the mapping of data between long term and transient storage. This code is not needed in persistent systems since it is exactly this functionality that is provided transparently by the persistent programming system. ....
IMS/VS Publications, IBM, White Plains, N.Y., 1978
High Availability Computer Systems - Jim Gray Daniel (1991) (10 citations) (Correct)
No context found.
IMS/XRF: Planning Guide, IBM, GC24-3151, IBM, White Plains, NY. 1987.
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