From bb991b972d3c76f9f2528916a77ff893cd433f99 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Sun, 29 Apr 2007 14:56:53 +0000 Subject: [PATCH] sentence clarify --- doc/build/content/metadata.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/build/content/metadata.txt b/doc/build/content/metadata.txt index 38785f3c50..054dbdde80 100644 --- a/doc/build/content/metadata.txt +++ b/doc/build/content/metadata.txt @@ -132,7 +132,7 @@ To bind `MetaData` to a single `Engine`, use `BoundMetaData`: # create the Engine and MetaData in one step meta = BoundMetaData('postgres://db/', **kwargs) -Another form of `MetaData` exists which allows connecting to any number of engines, within the context of the current thread. This is `DynamicMetaData`: +Another form of `MetaData` exists which can connect to an engine within the context of the current thread only, allowing different engines to be connected within other concurrent threads. This is `DynamicMetaData`: {python} meta = DynamicMetaData() @@ -141,7 +141,7 @@ Another form of `MetaData` exists which allows connecting to any number of engin meta.connect('mysql://user@host/dsn') # create a new Engine and connect -`DynamicMetaData` is ideal for applications that need to use the same set of `Tables` for many different database connections in the same process, such as a CherryPy web application which handles multiple application instances in one process. +`DynamicMetaData` is intended for applications that need to use the same set of `Tables` for many different database connections in the same process, such as a CherryPy web application which handles multiple application instances in one process. #### Using the global Metadata object -- 2.47.2