otl3_whatn_1.htm

ISO_C++:C++_OTL开发文档

            <br>
          </li>
        </ul>
        </td>
      </tr>
      <tr>
        <td style="vertical-align: top;">New (in OTL 4.0.116):<br>
        <br>
        <ul>
          <li>A typo in otlv4.h in OTL 4.0.115 (line 3072) has been
fixed in this release.<br>
            <br>
          </li>
          <li><a href="otl3_stream_class.htm#create_stored_proc_call">otl_stream::create_stored_proc_call(</a>)
has been enhanced to do the following, which actually corresponds the
Oracle standard name resolution::<br>
            <br>
          </li>
          <ul>
            <li>sp in current schema</li>
            <li>private synonym for sp</li>
            <li>public synonym for sp</li>
          </ul>
        </ul>
        <br>
        </td>
      </tr>
      <tr>
        <td style="vertical-align: top;">New (in OTL 4.0.115):<br>
        <br>
        <ul>
          <li>OTL stream <a href="otl3_stream_class.htm#buffer_size">buffer
size</a>'s datatype was changed in this release from <span
 style="font-style: italic;">short int</span> to <span
 style="font-style: italic;">int</span>. See examples <a
 href="otl4_ex307.htm">307</a>, <a href="otl4_ex308.htm">308</a>, <a
 href="otl4_ex309.htm">309</a>, <a href="otl4_ex310.htm">310 </a>for
more detail.<br>
            <br>
          </li>
          <li>New #define <a
 href="otl3_compile.htm#OTL_STREAM_LEGACY_BUFFER_SIZE_TYPE">OTL_STREAM_LEGACY_BUFFER_SIZE_TYPE</a>
is introduced. It can be used to turn the stream old <span
 style="font-style: italic;">short int</span> buffer size back on. <br>
            <br>
          </li>
          <li><a href="otl3_bind_variables.htm#PLSQL_table_size">Maximum
size</a> of PL/SQL tables is no longer limited to 32767. See example <a
 href="otl4_ex311.htm">311</a>, <a href="otl4_ex312.htm">312 </a>for
more detail. #define <a
 href="otl3_compile.htm#OTL_STREAM_LEGACY_BUFFER_SIZE_TYPE">OTL_STREAM_LEGACY_BUFFER_SIZE_TYPE</a>
can also be used to turn the maximum size of PL/SQL tables back on. <br>
            <br>
          </li>
          <li>new <a href="otl3_bind_variables.htm#charz">charz</a>[]
datatype for PL/SQL tables of CHAR(XXX). See example <a
 href="otl4_ex313.htm">313</a>, <a href="otl4_ex314.htm">314 </a>for
more
detail.<br>
            <br>
          </li>
        </ul>
        </td>
      </tr>
      <tr>
        <td style="vertical-align: top;">New (in OTL 4.0.114):<br>
        <br>
        <ul>
          <li>Visual Age C++ (AIX) issues a warning when <a
 href="otl3_compile.htm#OTL_ORA7">OTL_ORA7</a> is enabled. The warning
has been fixed in this release.<br>
            <br>
          </li>
          <li>New #define <a href="otl3_compile.htm#OTL_INFORMIX_CLI">OTL_INFORMIX_CLI</a>
(Informix CLI for Unix) is introduced. It should be used in a
combination with #define <a href="otl3_compile.htm#OTL_ODBC_UNIX">OTL_ODBC_UNIX</a>.
            <br>
            <br>
          </li>
          <li>Basic support for <a href="http://www.timesten.com">TimeTen</a>
via ODBC (#define <a href="otl3_compile.htm#OTL_ODBC">OTL_ODBC</a>).
See examples <a href="otl4_t10_examples.htm">293-299</a> for more
detail.<br>
            <br>
          </li>
          <li>Basic support for Microoft ACCESS <span
 style="text-decoration: underline;"></span>via ODBC (#define <a
 href="file:///D%7C/oscl/vc/doc/otl4/otl3_compile.htm#OTL_ODBC">OTL_ODBC</a>).
See examples <a href="otl4_msaccess_examples.htm">300-306</a> for more
detail.<br>
            <br>
          </li>
          <li><a name="OTL40114"></a>When <a
 href="otl4_stream_read_iterator.htm">OTL
stream read iterator</a> is used with Forte C++ on Solaris, the program
may crash with a "bus error". The problem is that the iterator's
internal buffers need to be aligned to the machine word (requirement on
Solaris). The bug has been fixed in this release. <br>
            <br>
          </li>
        </ul>
        </td>
      </tr>
      <tr>
        <td style="vertical-align: top;">New (in OTL 4.0.113):<br>
        <br>
        <ul>
          <li>The following new #define: <span
 style="font-family: monospace;"><a
 href="otl3_compile.htm#OTL_ODBC_SELECT_STM_EXECUTE_BEFORE_DESCRIBE">OTL_ODBC_SELECT_STM_EXECUTE_BEFORE_DESCRIBE</a>.
            </span>It changes the OTL stream's default behavior for
SELECT statements: SELECT gets prepared, executed, and only then the
SELECT statement columns get described. New versions (PostgreSQL 8.0,
MySQL 5.0 (still in beta)) of some databases require this change.<br>
            <br>
          </li>
          <li>Some fragments of redundant, conditionally compiled code
were cleaned up.<br>
            <br>
          </li>
        </ul>
        </td>
      </tr>
      <tr>
        <td style="vertical-align: top;">New (in OTL4.0.112):<br>
        <br>
        <ul>
          <li>Following new #define is introduced in this release:
#define <a
 href="otl3_compile.htm#OTL_ORA_DECLARE_COMMON_READ_STREAM_INTERFACE">OTL_ORA_DECLARE_COMMON_READ_STREAM_INTERFACE</a>.
It enables a common interface class, which both <a
 href="otl3_stream_class.htm">otl_stream</a> and <a
 href="otl4_refcur_stream.htm">otl_refcur_stream</a> derive from. See
also example <a href="otl4_ex292.htm">292</a>.<br>
            <br>
          </li>
          <li>When OTL stream <a href="otl3_stream_pooling.htm">pooling</a>
is enabled (#define <a href="otl3_compile.htm#OTL_STREAM_POOLING_ON">OTL_STREAM_POOLING_ON</a>),
in the case of a database error, if otl_stream::<a
 href="otl3_stream_class.htm#clean">clean</a>() gets called, it does
not reset some internal flags correctly, so that the stream cannot be
reused without being closed and reopened.&nbsp; The bug is fixed in
this release.<br>
            <br>
          </li>
          <li><a href="otl3_stream_class.htm#otl_column_desc">otl_column_desc</a>
class was extended in OTL 4.0.110 with the following <a
 href="otl3_stream_class.htm#charset_form">fields</a>: charset_form,
char_size. The fields are enabled with <a
 href="otl3_compile.htm#OTL_UNICODE">OTL_UNICODE</a> and&nbsp; #defines
OTL_ORA8i/9i/10g. A mistake
was made for OCI8i: OCI8i does not provide the "char size" information.
The char_size field will be set to 0 instead. If anybody has a
different opinion on this, let me know.</li>
        </ul>
        </td>
      </tr>
      <tr>
        <td style="vertical-align: top;">New (in OTL 4.0.111):<br>
        <br>
        <ul>
          <li>Following new #define is introduced in this release:
#define <a
 href="otl3_compile.htm#OTL_STRICT_NUMERIC_TYPE_CHECK_ON_SELECT">OTL_STRICT_NUMERIC_TYPE_CHECK_ON_SELECT.</a>
See also examples <a href="otl4_ex288.htm">288 (OCI7)</a>, <a
 href="otl4_ex289.htm">289 (OCI8i/9i/10g)</a>, <a href="otl4_ex290.htm">290</a><a
 href="otl4_ex290.htm"> (DB2 CLI)</a>, <a href="otl4_ex291.htm">291</a><a
 href="otl4_ex291.htm"> (MSSQL)</a>.<br>
            <br>
          </li>
          <li><a name="40111"></a>When #define <a
 href="otl3_compile.htm#OTL_UNICODE">OTL_UNICODE</a>
is enabled&nbsp; for OTL/OCI8i/9i/10g, maxmium string size char[XXX]
bind variables (char[4001] for VARCHAR2, and char[2001] for NVARCHAR2
data types) may cause the "Invalid length" Oracle error. The bug is
fixed in this release.<br>
            <br>
          </li>
        </ul>
        </td>
      </tr>
      <tr>
        <td style="vertical-align: top;">New (in OTL 4.0.110):<br>
        <br>
        <ul>
          <li>When&nbsp; #define <a href="otl3_compile.htm#OTL_ODBC">OTL_ODBC</a>
is enabled, and when the OTL header file is being compiled in the <a
 href="http://www.unixodbc.org">unixODBC</a> driver manager
environment, the C++ compiler reports the following wide character
related #defines as missing: SQL_WVARCHAR, SQL_WCHAR, SQL_WLONGVARCHAR,
SQL_C_WCHAR.&nbsp; The compilation errors are fixed is this release.<br>
            <br>
          </li>
          <li><a href="otl3_stream_class.htm#otl_column_desc">otl_column_desc</a>
class has been extended with the following <a
 href="otl3_stream_class.htm#charset_form">fields</a>: charset_form,
char_size. The fields are enabled when&nbsp; <a
 href="otl3_compile.htm#OTL_UNICODE">OTL_UNICODE</a> and <a
 href="otl3_compile.htm#OTLORA9I">OTL_ORA9I</a> / <a
 href="otl3_compile.htm#OTL_ORA10G">OTL_ORA10G</a> are defined. See
also example <a href="otl4_ex287.htm">287</a><br>
          </li>
        </ul>
        </td>
      </tr>
      <tr>
        <td style="vertical-align: top;">New (in OTL 4.0.109):<br>
        <br>
        <ul>
          <li>OTL/OCI8i/9i/10g introduces the following new bind
variable datatypes: <a href="otl3_bind_variables.htm#nchar">nchar</a>[],
            <a href="otl3_bind_variables.htm#nclob">nclob</a>. nchar[]
is intended for special cases when, say, both VARCHAR2 and NVARCHAR2
need to be declared inthe SQL statement. nclob is useful for cases when
both CLOB and NCLOB need to be declared in the same SQL statement. <br>
            <br>
For
more detail, see examples <a href="otl4_ex285.htm">285</a>, <a
 href="otl4_ex286.htm">286</a>.<br>
            <br>
          </li>
        </ul>
        </td>
      </tr>
      <tr>
        <td style="vertical-align: top;"><a name="otl40108"></a>New (in
OTL 4.0.108):<br>
        <br>
        <ul>
          <li>Basic support for <a href="otl3_compile.htm#OTL_UNICODE">Unicode</a>
data strings in OTL/ODBC and OTL/DB2-CLI. See the following examples
for
more detail:<br>
            <br>
          </li>
          <ul>
            <li><a href="otl4_db2_unicode_examples.htm">DB2 Unicode /
CLI</a></li>
            <li><a href="otl4_mssql_unicode_examples.htm">MS SQL Server
Unicode / ODBC</a></li>
            <li><a href="otl4_ora_odbc_unicode_examples.htm">Oracle
8/8i/9i/10g Unicode / ODBC<br>
              <br>
              </a></li>
          </ul>
          <li>Support for <a href="http://sqlite.org">SQLite</a> via
ODBC. See the <a href="otl4_sqlite_examples.htm">examples</a> for
SQLite for more detail.<br>
            <br>
          </li>
          <li>OTL <a href="otl3_faq.htm">FAQ</a> was updated.<br>
          </li>
        </ul>
        <br>
        </td>
      </tr>
      <tr>
        <td style="vertical-align: top;">New (in OTL 4.0.0.107):<br>
        <br>
        <ul>
          <li>This release is a quick fix for a compilation bug that
was introduced in OTL 4.0.106 along with the support for iODBC for BSD
Unix.</li>
        </ul>
        </td>
      </tr>
      <tr>
        <td style="vertical-align: top;">New (in OTL 4.0.106):<br>
        <br>
        <ul>
          <li>New #define is introduced: #define <a
 href="otl3_compile.htm#OTL_IODBC_BSD">OTL_IODBC_BSD</a>. This #define
should be enabled when the iODBC ODBC driver manager is used in BSD
Unix.<br>
            <br>
          </li>
          <li>OTL/ODBC now supports&nbsp; <a
 href="http://firebird.sourceforge.net/">Firebird Database</a>. See
also the Firebird / ODBC code <a href="otl4_interbase_examples.htm">examples</a>.<br>
            <br>
          </li>
          <li>New <a href="otl3_exception_class.htm">otl_exception</a>
is introduced: <small><font style="font-style: italic;" size="+1"><small>otl_stream::<a
 href="file:///D%7C/oscl/vc/doc/otl4/otl3_stream_class.htm#operator_int">operator
int</a>() is not supported in the <a
 href="otl3_stream_class.htm#set_lob_stream_mode">LOB stream mode</a> </small></font><font
 size="+1"><small>(code <a href="otl3_exc_list.htm#32025">32025)</a>.
This exception enforces the </small></font><font
 style="font-style: italic;" size="+1"><small><a
 href="otl3_stream_class.htm#operator_int">operator int()</a></small></font><font
 size="+1"><small> limits.</small></font></small><font
 style="font-style: italic;" size="+1"><a
 href="file:///D%7C/oscl/vc/doc/otl4/otl3_stream_class.htm#operator_int"