Oracle C++ Call Interface Programmer's Guide

Overview of the OUTTYPE File
OCCI_STD_NAMESPACE::vector< object_type * > the_table;
oracle::occi::Date the_date;
oracle::occi::Number the_num;
oracle::occi::Bytes the_raw;
public:
};
void *operator new(size_t size);
void *operator new(size_t size, const oracle::occi::Connection * sess,
const OCCI_STD_NAMESPACE::string& table);
OCCI_STD_NAMESPACE::string getSQLTypeName() const;
many_types();
many_types(void *ctxOCCI_) : oracle::occi::PObject (ctxOCCI_) { };
static void *readSQL(void *ctxOCCI_);
virtual void readSQL(oracle::occi::AnyData& streamOCCI_);
static void writeSQL(void *objOCCI_, void *ctxOCCI_);
virtual void writeSQL(oracle::occi::AnyData& streamOCCI_);
#endif
For C++, when TRANSITIVE=TRUE, the OTT utility automatically translates any
types that are used as attributes of a type being translated, including types that are
only being accessed by a pointer or REF in an object type attribute. Even though
only the many_types object was specified in the INTYPE file for the C++ example,
a class declaration was generated for all the object types, including the other_
type object, which was only accessed by a REF in the many_types object.
Overview of the OUTTYPE File
The OUTTYPE file is named on the OTT command line. When the OTT utility
generates a C or C++ header file, it also writes the results of the translation into the
OUTTYPE file. This file contains an entry for each of the translated types, including
7-26 Oracle C++ Call Interface Programmer’s Guide