[Checkins] SVN: z3c.saconfig/trunk/src/z3c/saconfig/README.txt More clarifications.

[Martijn Faassen]

Log message for revision 87591:
  More clarifications.
  

Changed:
  U   z3c.saconfig/trunk/src/z3c/saconfig/README.txt

-=-
Modified: z3c.saconfig/trunk/src/z3c/saconfig/README.txt
===================================================================
--- z3c.saconfig/trunk/src/z3c/saconfig/README.txt	2008-06-20 11:42:16 UTC (rev 87590)
+++ z3c.saconfig/trunk/src/z3c/saconfig/README.txt	2008-06-20 12:02:12 UTC (rev 87591)
@@ -9,9 +9,20 @@
 component architecture. This package is based on ``zope.sqlalchemy``, which
 offers transaction integration between Zope and SQLAlchemy.
 
-GloballyScopedSession
-=====================
+We sketch out two main scenarios here:
 
+* one database per Zope 3 instance.
+
+* one database per site (or Grok application) in a Zope 3 instance
+  (and thus multiple databases per Zope 3 instance).
+
+This package does not provide facilities to allow multiple databases
+in a single site; if you want more than one database in your Zope 3
+instance, you will need to set up different sites.
+
+GloballyScopedSession (one database per Zope 3 instance)
+========================================================
+
 The simplest way to set up SQLAlchemy for Zope is to have a single
 thread-scoped session that's global to your entire Zope
 instance. Multiple applications will all share this session. The
@@ -129,8 +140,8 @@
   >>> bob.addresses
   []
 
-SiteScopedSession
-=================
+SiteScopedSession (one database per site)
+=========================================
 
 In the example above we have set up SQLAlchemy with Zope using
 utilities, but it did not gain us very much, except that you can just