Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- CA-Clipper 5.3 . Technical Reference - <b>gohot()</b> http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
 goHot()
 Mark the work area data buffer as hot
------------------------------------------------------------------------------
 Prototype

     ERRCODE goHot(
                       AREAP wa
                    )

 Arguments

     wa is a pointer to self.

 Description

     goHot() informs the RDD that data in memory is not guaranteed to match
     data in the data store (usually a disk).

 Default Behavior

     You must implement the default behavior of this method through a
     subclass.

 Implementation Notes

     .  The concept of hot and cold refers to the current state of
        information in memory as it relates to information on disk.  If the
        information in memory, has changed since last written to disk, it is
        considered hot.  A cold work area's memory is in sync with its disk-
        based counterpart.

     .  When a work area goes hot in a shared environment, you must be
        certain that all necessary locks are in place.  Going hot indicates
        that a write is about to be performed on data.

     .  You must never allow work areas marked as wa->fReadonly to call
        goHot().  This is an ideal place to generate runtime recoverable
        errors indicating that locks must be present or the work area must not
        be in a read-only mode.

     .  wa should remain hot until it is marked cold by goCold().

 Files  Header file is Rdd.api.


See Also: AREA goCold()

Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson