<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="/oai-pmh.xsl"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-09-20T12:38:08Z</responseDate>
  <request identifier="oai:www.ideals.illinois.edu:2142/81922" metadataPrefix="etdms" verb="GetRecord">https://www.ideals.illinois.edu/oai-pmh</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:www.ideals.illinois.edu:2142/81922</identifier>
        <datestamp>2023-07-11</datestamp>
        <setSpec>col_2142_5131</setSpec>
        <setSpec>col_2142_10761</setSpec>
        <setSpec>com_2142_5130</setSpec>
        <setSpec>com_2142_10755</setSpec>
        <setSpec>com_2142_234</setSpec>
      </header>
      <metadata>
        <thesis xmlns="http://www.ndltd.org/standards/metadata/etdms/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dc="http://purl.org/dc/elements/1.1/" xsi:schemaLocation="http://www.ndltd.org/standards/metadata/etdms/1.1/ http://www.ndltd.org/standards/metadata/etdms/1.1/etdms11.xsd http://purl.org/dc/elements/1.1/ http://www.ndltd.org/standards/metadata/etdms/1.1/etdmsdc.xsd">
          <dc:contributor>Belford, Geneva G.</dc:contributor>
          <dc:creator>Voss, William Eric</dc:creator>
          <dc:date>2015-09-25T20:21:00Z</dc:date>
          <dc:date>2015-09-25T20:21:00Z</dc:date>
          <dc:date>10000-01-01</dc:date>
          <dc:date>1998</dc:date>
          <dc:date>1998</dc:date>
          <dc:description>To recompute from scratch, cache, or maintain a running-total is a database optimization question. The best answer depends in part upon usage patterns. For example, is total accessed frequently, or is the underlying table updated frequently? These usage patterns cannot necessarily be accurately predicted during application design. I describe materialization cost estimates based on having the database observe and collect data on actual usage patterns, and the actual costs observed implementing different choices. I designed an intelligent system which dynamically makes materialization choices using these cost estimates. The system is adaptive, and switches between the possible materialization choices as usage patterns change.</dc:description>
          <dc:description>Made available in DSpace on 2015-09-25T20:21:00Z (GMT). No. of bitstreams: 2
license.txt: 4848 bytes, checksum: 96035ab3f5e1c23cc7138a224ce498bd (MD5)
9904612.pdf: 3708125 bytes, checksum: 9dc3e9320145fef9586490afd44aac66 (MD5)
  Previous issue date: 1998</dc:description>
          <dc:description>Embargo set by: Seth Robbins for item 83203
Lift date: Forever
Reason: Restricted to the U of I community idenfinitely during batch ingest of legacy ETDs</dc:description>
          <dc:description>Restricted to the U of I community idenfinitely during batch ingest of legacy ETDs</dc:description>
          <dc:description>U of I Only</dc:description>
          <dc:description>107 p.</dc:description>
          <dc:description>Thesis (Ph.D.)--University of Illinois at Urbana-Champaign, 1998.</dc:description>
          <dc:identifier>http://hdl.handle.net/2142/81922</dc:identifier>
          <dc:identifier>(MiAaPQ)AAI9904612</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:subject>Computer Science</dc:subject>
          <dc:title>Caching Derived Data in Object-Oriented Databases, and an Intelligent System Design for Selecting Their Materialization Strategies</dc:title>
          <dc:type>text</dc:type>
          <degree>
            <department>Computer Science</department>
            <discipline>Computer Science</discipline>
            <grantor>University of Illinois at Urbana-Champaign</grantor>
            <level>Dissertation</level>
            <name>Ph.D.</name>
          </degree>
        </thesis>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
