OTL 4.0, Examples for Oracle 8i, Unicode
The examples below show how to use OTL with Oracle 8i and Unicode
based strings. At the database level,, the string format may vary,
and at least at the C++ level all string data gets converted
into 2-byte Unicode. In order to enable OTL/OCI8I and Unicode,
the following #defined need to be defined: #define OTL_ORA8I, #define OTL_UNICODE.
- Example 174 (Unicode
Insert/Select with std::array<char16_t,...>)
- Example 175 (Simple Unicode
Insert/Select in the NLS (NVARCHAR2))
- Example 176 (Unicode Insert and
Select via referenced cursor)
- Example 177 (Simple Unicode
Insert/Select with LONG)
- Example 178 (Simple Unicode
Insert/Select with CLOB)
- Example 179 (Simple Unicode
Insert/Select with NCLOB)
- Example 180 (Simple Unicode
Insert/Select with CLOB via referenced cursor)
- Example 181 (Simple Unicode
Insert/Select with NCLOB via referenced cursor)
- Example 182 (Simple Unicode
Insert/Select with CLOB, and LOB streams)
- Example 183 (Simple Unicode
Insert/Select with NCLOB, and LOB streams)
- Example 184 (Unicode, VARCHAR2,
and otl_refcur_stream)
- Example 185 (Unicode, NVARCHAR2,
and otl_refcur_stream)
- Example 186 (Unicode,
PLSQL/index-by tables as parameters)
- Example 187 (Unicode,
PLSQL/index-by tables as parameters, and NVARCHAR2s)
- Example 285 (Simple Unicode
Insert/Select for both VARCHAR2 and NVARCHAR2 at the same
time)
- Example 286 (Simple Unicode
Insert/Select for both CLOB and NCLOB at the
same time)
- Example 287
(otl_stream::describe_select() with extended otl_column_desc
fields)
- Example 751 (OTL stream pooling
and #define OTL_UNICODE_STRING_TYPE)
Prev NextContentsGo Home
Copyright © 1996-2024, Sergei Kuchin, email: skuchin@gmail.com, skuchin@gmail.com
.
Permission to use, copy, modify and redistribute this document
for any purpose is hereby granted without fee, provided that the
above copyright notice appear in all copies. THE SOFTWARE IS
PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE
LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE
USE OR PERFORMANCE OF THIS SOFTWARE.