Limitations – Sun Microsystems Sun StorageTek 5800 User Manual
Page 45
–
–
“hc_nvr_get_timestamp” on page 83
–
–
–
“hc_pstmt_set_string” on page 101
–
“hc_pstmt_set_char” on page 102
–
“hc_pstmt_set_double” on page 103
–
“hc_pstmt_set_long” on page 104
–
“hc_pstmt_set_date” on page 105
–
“hc_pstmt_set_time” on page 106
–
“hc_pstmt_set_timestamp” on page 107
–
“hc_pstmt_set_binary” on page 108
–
“hc_pstmt_query_ez” on page 109
–
“hc_qrs_is_query_complete” on page 97
–
“hc_qrs_get_query_integrity_time” on page 98
The following functions have changed in the API:
■
■
The following functions and types have been removed from the API:
■
hc_query_plus_result_set_t
■
hc_query_plus_ez
■
hc_qprs_next_ez
■
hc_qprs_free
Limitations
This release of the synchronous C API is subject to the following limitations:
■
Changes to the metadata schema at the server are only detected at the client at the next call
to
“hc_session_create_ez” on page 53
■
The values returned by
“hc_session_get_platform_result” on page 58
will not be
updated properly after calls to the functions
and
■
When using the C API, the maximum metadata size of a data item stored using either
or
“hc_store_metadata_ez” on page 88
is limited to
approximately 76300 bytes. The exact maximum metadata size depends on many factors
and should not be relied on. This limitation does not apply to metadata stored using the Java
API.
Synchronous C API
Chapter 3 • Sun StorageTek 5800 System C Client API
45