From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Thu, 23 Sep 2010 23:24:28 +0000 (-0400)
Subject: doc edits
X-Git-Tag: rel_0_6_5~48
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=21d2a6d790983054e4d008af991b7dda309a94c4;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

doc edits
---

diff --git a/doc/build/dialects/index.rst b/doc/build/dialects/index.rst
index a8cfc33245..8ad9330bcc 100644
--- a/doc/build/dialects/index.rst
+++ b/doc/build/dialects/index.rst
@@ -3,22 +3,23 @@
 Dialects
 ========
 
-The *dialect* is the system SQLAlchemy uses to communicate with various types of DBAPIs and databases.
-A compatibility chart of supported backends can be found at :ref:`supported_dbapis`.
+The **dialect** is the system SQLAlchemy uses to communicate with various types of DBAPIs and databases.
+A compatibility chart of supported backends can be found at :ref:`supported_dbapis`.  The sections that 
+follow contain reference documentation and notes specific to the usage of each backend, as well as notes
+for the various DBAPIs.
 
-This section contains all notes and documentation specific to the usage of various backends.
-
-Supported Databases
--------------------
-
-These backends are fully operational with 
-current versions of SQLAlchemy.
+Note that not all backends are fully ported and tested with
+current versions of SQLAlchemy. The compatibility chart
+should be consulted to check for current support level.
 
 .. toctree::
     :maxdepth: 1
     :glob:
 
     firebird
+    informix
+    maxdb
+    access
     mssql
     mysql
     oracle
@@ -26,17 +27,4 @@ current versions of SQLAlchemy.
     sqlite
     sybase
 
-Unsupported Databases
----------------------
-
-These backends are untested and may not be completely
-ported to current versions of SQLAlchemy.
-
-.. toctree::
-    :maxdepth: 1
-    :glob:
-
-    access
-    informix
-    maxdb
 
diff --git a/doc/build/index.rst b/doc/build/index.rst
index 2c66bd47f2..2d75a5c08f 100644
--- a/doc/build/index.rst
+++ b/doc/build/index.rst
@@ -8,7 +8,7 @@ Table of Contents
     orm/index
     core/index
     dialects/index
-
+    
 Indices and tables
 ------------------
 
diff --git a/lib/sqlalchemy/dialects/sqlite/pysqlite.py b/lib/sqlalchemy/dialects/sqlite/pysqlite.py
index 575cb37f20..b2295f49b4 100644
--- a/lib/sqlalchemy/dialects/sqlite/pysqlite.py
+++ b/lib/sqlalchemy/dialects/sqlite/pysqlite.py
@@ -68,12 +68,13 @@ pysqlite's driver does not.   Additionally, SQLAlchemy does not at
 this time automatically render the "cast" syntax required for the 
 freestanding functions "current_timestamp" and "current_date" to return
 datetime/date types natively.   Unfortunately, pysqlite 
-does not provide the standard DBAPI types in `cursor.description`,
+does not provide the standard DBAPI types in ``cursor.description``,
 leaving SQLAlchemy with no way to detect these types on the fly 
 without expensive per-row type checks.
 
-Usage of PARSE_DECLTYPES can be forced if one configures 
-"native_datetime=True" on create_engine()::
+Keeping in mind that pysqlite's parsing option is not recommended,
+nor should be necessary, for use with SQLAlchemy, usage of PARSE_DECLTYPES 
+can be forced if one configures "native_datetime=True" on create_engine()::
 
     engine = create_engine('sqlite://', 
                     connect_args={'detect_types': sqlite3.PARSE_DECLTYPES|sqlite3.PARSE_COLNAMES},