Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!uw-beaver!ubc-cs!alberta!cpsc.ucalgary.ca!news
From: gintera@cs-sun-fsd.cpsc.ucalgary.ca (Andrew Ginter)
Newsgroups: comp.object
Subject: Re: Stash Collection
Summary: ODB's do this
Keywords: object caching
Message-ID: <1990Nov28.180340.14554@cpsc.ucalgary.ca>
Date: 28 Nov 90 18:03:40 GMT
References: <2849@esquire.dpw.com>
Organization: U. of Calgary Computer Science
Lines: 19
Nntp-Posting-Host: cs-sun-fsd

Some object databases do a subset of what you're asking for.  These
databases cache objects in memory.  When things get full up, or at the
end of a transaction, or whenever else it makes sense, objects are
flushed to the database and references to the objects are "fixed".  If
anyone tries to chase a "fixed" reference, the indicated object is
fetched back into memory.  The Postgres system is described in:

  A Shared Object Hierarchy, by Lawrence A. Rowe.

The paper is available via ftp from postgres.berkeley.edu as part of
the Postgres papers "tar" file.

The Orion system is described in:

  Integrating an Object-Oriented Programming System with a Database
  Sytem, by Won Kim, Bat Ballou, Hong-Tai Chou, Jorge F. Garza, Darrel
  Woelk and Jay Banerjee, OOPSLA '88 Proceedings

Andrew Ginter, 403-282-2984, gintera@cpsc.ucalgary.ca, Ginter@uncamult.bitnet