From 27f7c595d216c8b1d87e5a3648ada09f684542d9 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Fri, 8 Jun 2012 15:55:08 -0400 Subject: Add some `Sphinx` paragraph level versions informations markups, such as ``.. versionadded::``, ``.. versionchanged::`` and ``.. deprecated::``. --- lib/sqlalchemy/dialects/oracle/base.py | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'lib/sqlalchemy/dialects/oracle/base.py') diff --git a/lib/sqlalchemy/dialects/oracle/base.py b/lib/sqlalchemy/dialects/oracle/base.py index 500b1995f..439568dd7 100644 --- a/lib/sqlalchemy/dialects/oracle/base.py +++ b/lib/sqlalchemy/dialects/oracle/base.py @@ -63,10 +63,12 @@ used on the SQLAlchemy side. Unicode ------- -SQLAlchemy 0.6 uses the "native unicode" mode provided as of cx_oracle 5. cx_oracle 5.0.2 -or greater is recommended for support of NCLOB. If not using cx_oracle 5, the NLS_LANG -environment variable needs to be set in order for the oracle client library to use -proper encoding, such as "AMERICAN_AMERICA.UTF8". +.. versionchanged:: 0.6 + SQLAlchemy uses the "native unicode" mode provided as of cx_oracle 5. + cx_oracle 5.0.2 or greater is recommended for support of NCLOB. + If not using cx_oracle 5, the NLS_LANG environment variable needs + to be set in order for the oracle client library to use proper encoding, + such as "AMERICAN_AMERICA.UTF8". Also note that Oracle supports unicode data through the NVARCHAR and NCLOB data types. When using the SQLAlchemy Unicode and UnicodeText types, these DDL types will be used -- cgit v1.2.1