When you query data from HDATA, the UNICOM Intelligence JDBC Driver converts data from the UNICOM Intelligence OLE DB Provider to the JAVA result set using the following rules:

A 64-bit floating-point number with at least 15 digits of precision.

JAVA result set: A single column: Double

A 32-bit signed integer.

JAVA result set: A single column: Integer

A character string. The maximum length of a text variable is dependent on the DSC. The string might or might not support Unicode, depending on how the CDSC has implemented its storage. The Provider implements all strings using Unicode.

JAVA result set: A single column: String

A single or multiple categorical response type. The maximum number of responses available varies between DSCs. A categorical response is implemented in the Provider as a string. The responses are in { } curly braces, with each response delimited by a comma. For example, {2,3,8} represents the responses 2, 3, and 8. Depending on how the data was collected, the order of responses in the string can be the order in which they were chosen in response to the question. This can be important for analysis.

JAVA result set: Column.Type is Categorical 129. The type is returned as a getTypeInfo method of DatabaseMetadata. The return value is determined by the connection properties. For more information, see Return category value.

A 64-bit OLE date. The OLE date type contains both date and time and it is represented using the DATE type.

JAVA result set: A single column: DATE

Not implemented.

JAVA result set: N/A

A Boolean value of either True or False. This is implemented internally using VARIANT_BOOL. However, when a Boolean is converted to a Long or a Double, it will be converted to 1 for True and 0 for False.

JAVA result set: A single column: Boolean

A hierarchical value. A level contains a child recordset.

JAVA result set: N/A for VDATA; a single BINARY column for HDATA

Also called a Loop. These represent loops, grids, and levels. The Array object defines a question or set of questions that are to be asked more than once.

JAVA result set: Multiple columns. For more information, see Query array field in VDATA or Query array field in HDATA.

These represent a grid question. A Grid object can be considered a special case of the Array object.

JAVA result set: Multiple columns. For more information, see Query class field in VDATA or “Query class field in HDATA”.

These group categorical and grid questions that share a category list, typically for presentation in a paper questionnaire.

JAVA result set: Multiple columns. For more information, see Query compound field in VDATA or “Query compound field in HDATA”.

These are used to group questions.

JAVA result set: Multiple columns. For more information, see Query grid field in VDATA or Query grid field in HDATA.

In HDATA, array fields are considered level. Querying a level field is same as querying all sub-fields of the level field. For more information, see Return level field.

You can query array object sub-fields from the array table. Array objects contain the specialty field LevelID, which is a sequential number in the current level.

Using data from the UNICOM Intelligence Developer Documentation Library household.mdd example:

The result data is:

In HDATA, grid fields are considered level. Querying a level field is same as querying all sub-fields of the level field. For more information, see Return level field.

You can query grid object sub-fields from the array table. Grid objects contain the specialty field LevelID, which is an element value of the current grid.

To return categorical values in JDBC, see Return category value.

Using data from the UNICOM Intelligence Developer Documentation Library museum.mdd example:

The result data is:

Using data from the UNICOM Intelligence Developer Documentation Library short_drinks.mdd example:

The result data is: