Predefined IDL datatypes

EAServer ships with predefined datatypes for use in declaring parameter and return value datatypes. Predefined datatypes include all CORBA base types (except for the CORBA::Any type) and equivalents for database result sets and other commonly used database column types such as date, time, and timestamp. Table 3-1 lists these types.

**Table 3-1: Predefined EAServer IDL datatypes**
CORBA IDL type	Description
boolean	One bit of binary data; a value that is either true or false
short	A 16-bit integer
long	A 32-bit integer
long long	A 64-bit integer
float	Single-precision IEEE floating point numbers
double	Double-precision IEEE floating point numbers
string	A sequence of characters of any length
BCD::Binary	Sequence of bytes
BCD::Decimal	Fixed-point decimal
BCD::Money	Same as decimal
MJD::Date	A date including year, month, day, hour, minute, second, and millisecond values
MJD::Time	Holds the time of day, including hours, minutes, seconds, milliseconds
MJD::Timestamp	Holds the same data as date, plus a nanoseconds value
TabularResults::ResultSet	A single table of relational database rows
TabularResults::ResultSets	A sequence of 0 or more ResultSet objects

For descriptions of the datatypes defined in the BCD, MJD, or TabularResults modules, see the documentation in the html/ir subdirectory of your EAServer installation. (Or, load the main EAServer HTML page in your Web browser, and click the Interface Repository link). If you use types from these modules, add an include directive for the appropriate module at the top of the module that defines your interface. For example:

#include <TabularResults.idl>

Internally, TabularResults.idl includes both BCD.idl and MJD.idl. You need not include BCD.idl and MJD.idl explicitly if you have already included TabularResults.idl.