@20776309

* env_chromium.cc should not export symbols.
* Fix MSVC warnings.
* Removed large value support.
* Fix broken reference to documentation file

git-svn-id: https://leveldb.googlecode.com/svn/trunk@24 62dab493-f737-651d-591e-8d6aee1b9529

2 files changed, 1 insertions, 23 deletions

diff --git a/doc/impl.html b/doc/impl.html
index b190d2c..dd09fea 100644
--- a/doc/impl.html
+++ b/doc/impl.html
@@ -57,15 +57,6 @@ These merges have the effect of gradually migrating new updates from
 the young level to the largest level using only bulk reads and writes
 (i.e., minimizing expensive seeks).
 
-<h2>Large value files</h2>
-<p>
-Each large value (greater than 64KB by default) is placed in a large
-value file (*.val) of its own.  An entry is maintained in the log
-and/or sorted tables that maps from the corresponding key to the
-name of this large value file.  The name of the large value file
-is derived from a SHA1 hash of the value and its length so that
-identical values share the same file.
-<p>
 <h2>Manifest</h2>
 <p>
 A MANIFEST file lists the set of sorted tables that make up each
@@ -220,9 +211,7 @@ So maybe even the sharding is not necessary on modern filesystems?
 compaction and at the end of recovery.  It finds the names of all
 files in the database.  It deletes all log files that are not the
 current log file.  It deletes all table files that are not referenced
-from some level and are not the output of an active compaction.  It
-deletes all large value files that are not referenced from any live
-table or log file.
+from some level and are not the output of an active compaction.
 
 </body>
 </html>
diff --git a/doc/index.html b/doc/index.html
index 2a83fc3..c2312b7 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -412,17 +412,6 @@ We might want to prefix <code>filename</code> keys with one letter (say '/') and
 over just the metadata do not force us to fetch and cache bulky file
 contents.
 <p>
-<h2>Large Values</h2>
-<p>
-<code>leveldb</code> has special treatment of large values (by default, a value
-of length greater than or equal to 64K is considered large, though a
-field in Options can be used to adjust this threshold).  Each such
-large value is placed in a separate operating system file, and the
-normal database blocks just contain pointers to such files.
-<p>
-Furthermore, if the same large value occurs multiple times in a single
-database, it will be stored just once.
-<p>
 <h1>Checksums</h1>
 <p>
 <code>leveldb</code> associates checksums with all data it stores in the file system.