[Zope-CVS] CVS: Products/DBTab - CHANGES.txt:1.5 dbtab.conf.in:1.6 version.txt:1.9

[Shane Hathaway]

Update of /cvs-repository/Products/DBTab
In directory cvs.zope.org:/tmp/cvs-serv10683

Modified Files:
	CHANGES.txt dbtab.conf.in version.txt 
Log Message:
Updated docs and bumped version.txt

=== Products/DBTab/CHANGES.txt 1.4 => 1.5 ===
--- Products/DBTab/CHANGES.txt:1.4	Fri Jan 31 18:36:57 2003
+++ Products/DBTab/CHANGES.txt	Thu Feb  6 16:17:52 2003
@@ -1,23 +1,25 @@
 
-Version 1.1-unreleased
+Version 1.1
 
   - Changed DBTab's mounting strategy so that mounted connections stay
     bound to a root connection.  This change is designed to:
 
     - eliminate issues with volatile attributes in application code
-      that cross mount boundaries.
+      that cross mount boundaries.  Now it's safe to use cross-database
+      volatile attributes.
 
     - eliminate the global registry of open connections, which seemed
       to have a rare race condition (ugh!)
 
     - go faster. :-) The mount point traversal penalty is much lower
-      now, since it's now legal to keep a volatile reference to the
+      now, since the mount point can keep a long-lived reference to the
       mounted object.
 
 
 Version 1.0.2
 
 - Updated to work with the latest BDBStorage and AdaptableStorage.
+
 
 Version 1.0.1
 


=== Products/DBTab/dbtab.conf.in 1.5 => 1.6 ===
--- Products/DBTab/dbtab.conf.in:1.5	Mon Jan  6 11:59:03 2003
+++ Products/DBTab/dbtab.conf.in	Thu Feb  6 16:17:52 2003
@@ -427,8 +427,9 @@
 ######################################################################
 ##
 ## If you have BDBStorage installed, here is how to set up a
-## Berkeley-backed storage.  (A lot of these directions are copied
-## from BerkeleyBase.py.)
+## Berkeley-backed storage.  BDBStorage, available in ZODB version
+## 3.2 and above, is the successor to bsddb3storage.  (A lot of these
+## directions are copied from BerkeleyBase.py.)
 ##
 ## BDBStorage provides two variants: BDBFullStorage and
 ## BDBMinimalStorage.  BDBFullStorage provides undo and versioning,
@@ -460,7 +461,7 @@
 # prefix=zodb_
 
 ## Berkeley storages need to be checkpointed occasionally, otherwise
-## automatic recover can take a huge amount of time.  You should set
+## automatic recovery can take a huge amount of time.  You should set
 ## up a checkpointing policy which trades off the amount of work done
 ## periodically against the recovery time.  Note that the Berkeley
 ## environment is automatically, and forcefully, checkpointed twice
@@ -491,7 +492,7 @@
 
 ## You can also improve performance by tweaking the Berkeley cache
 ## size.  Berkeley's default cache size is 256KB which is usually too
-## small.  Our default cache size is 128MB which seems like a useful
+## small.  The default cache size is 128MB which seems like a useful
 ## tradeoff between resource consumption and improved performance.
 ## You might be able to get slightly better results by turning up the
 ## cache size, although be mindful of your system's limits.  See here
@@ -503,7 +504,7 @@
 
 # cachesize=135000000
 
-## These attributes control the autopacking thread: ## frequency is
+## These attributes control the autopacking thread: frequency is
 ## the time in seconds after which an autopack phase will be
 ## performed.  E.g. if frequency is 3600, an autopack will be done
 ## once per hour.  Set frequency to 0 to disable autopacking (the


=== Products/DBTab/version.txt 1.8 => 1.9 ===
--- Products/DBTab/version.txt:1.8	Fri Jan 31 18:34:50 2003
+++ Products/DBTab/version.txt	Thu Feb  6 16:17:52 2003
@@ -1 +1 @@
-DBTab-1.1-unreleased
+DBTab-1.1