(no commit message)

diff --git a/doc/build/content/pooling.myt b/doc/build/content/pooling.myt
index 3b7545e929c04a35ecff937b97566a9ace6cc940..209b3313b3806726a028e51b043ae44589f22cf2 100644 (file)
--- a/doc/build/content/pooling.myt
+++ b/doc/build/content/pooling.myt
@@ -1,5 +1,6 @@
 <%flags>inherit='document_base.myt'</%flags>
 <&|doclib.myt:item, name="pooling", description="Connection Pooling" &>
+    <P><b>Note:</b>This section describes the connection pool module of SQLAlchemy, which is the smallest component of the library that can be used on its own.  If you are interested in using SQLAlchemy for query construction or Object Relational Mapping, this module is automatically managed behind the scenes; you can skip ahead to <&formatting.myt:link,path="dbengine"&> in that case.</p>
     <p>At the base of any database helper library is a system of efficiently acquiring connections to the database.  Since the establishment of a database connection is typically a somewhat expensive operation, an application needs a way to get at database connections repeatedly without incurring the full overhead each time.  Particularly for server-side web applications, a connection pool is the standard way to maintain a "pool" of database connections which are used over and over again among many requests.  Connection pools typically are configured to maintain a certain "size", which represents how many connections can be used simultaneously without resorting to creating more newly-established connections.
     </p>
     <p>SQLAlchemy includes a pooling module that can be used completely independently of the rest of the toolset.  This section describes how it can be used on its own, as well as the available options.  If SQLAlchemy is being used more fully, the connection pooling described below occurs automatically.  The options are still available, though, so this core feature is a good place to start.