com.ibm.etools.iseries.comm.interfaces
Interface IDataBaseFieldConstants
- All Known Implementing Classes:
- ISeriesHostDatabaseField, QSYSHostDatabaseField, QSYSRemoteDatabaseField
public interface IDataBaseFieldConstants
Field type constants for database fields.
Copyright
static final String Copyright
- See Also:
- Constant Field Values
FLDTYPE_BINARY
static final int FLDTYPE_BINARY
- See Also:
- Constant Field Values
FLDTYPE_FLOAT
static final int FLDTYPE_FLOAT
- See Also:
- Constant Field Values
FLDTYPE_ZONED
static final int FLDTYPE_ZONED
- See Also:
- Constant Field Values
FLDTYPE_PACKED
static final int FLDTYPE_PACKED
- See Also:
- Constant Field Values
FLDTYPE_ALPHA
static final int FLDTYPE_ALPHA
- See Also:
- Constant Field Values
FLDTYPE_VALPHA
static final int FLDTYPE_VALPHA
- See Also:
- Constant Field Values
FLDTYPE_PUREDBCS
static final int FLDTYPE_PUREDBCS
- See Also:
- Constant Field Values
FLDTYPE_DBCS
static final int FLDTYPE_DBCS
- See Also:
- Constant Field Values
FLDTYPE_FLOATD
static final int FLDTYPE_FLOATD
- See Also:
- Constant Field Values
FLDTYPE_HEX
static final int FLDTYPE_HEX
- See Also:
- Constant Field Values
FLDTYPE_UNKNOWN
static final int FLDTYPE_UNKNOWN
- See Also:
- Constant Field Values
FLDTYPE_VDBCS
static final int FLDTYPE_VDBCS
- See Also:
- Constant Field Values
FLDTYPE_DATE
static final int FLDTYPE_DATE
- See Also:
- Constant Field Values
FLDTYPE_TIME
static final int FLDTYPE_TIME
- See Also:
- Constant Field Values
FLDTYPE_TIMESTAMP
static final int FLDTYPE_TIMESTAMP
- See Also:
- Constant Field Values
FLDTYPE_MAX
static final int FLDTYPE_MAX
- See Also:
- Constant Field Values
FLDTYPE_GRAPHIC
static final int FLDTYPE_GRAPHIC
- See Also:
- Constant Field Values
FLDTYPE_VGRAPHIC
static final int FLDTYPE_VGRAPHIC
- See Also:
- Constant Field Values
Copyright © 2011 IBM Corp. All Rights Reserved.
Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.