CUBRID PHP Library release notes


2008 R3.1 Release

This release is a major release. CUBRID 3.1 Stable has been released. Several new features have been added to this version
including new BLOB and CLOB data types and new APIs in JDBC/CCI which can get foreign key information. Accordingly new 
functions and features are added in this CUBRID PHP version, and some bugs have been fixed.

Functionality added:

The following functions have been added, and documents of all functions have been updated.
CUBRID-MySQL Compatibility functions Lob related functions
cubrid_query
cubrid_close
cubrid_error
cubrid_errno
cubrid_client_encoding
cubrid_fetch_array
cubrid_db_name
cubrid_ping
cubrid_lob_get
cubrid_lob_close
cubrid_lob_size
cubrid_lob_export
cubrid_lob_send

Functionality removed:

Glo data type has been removed from CUBRID 3.1, BLOB/CLOB can be used to replace it.
Glo related functions
cubrid_new_glo
cubrid_save_to_glo
cubrid_load_from_glo
cubrid_send_glo

Changed and Enhanced Features:

1.) Add three new schema type integer constants for cubrid_schema(): 

    CUBRID_SCH_IMPORTED_KEYS
    CUBRID_SCH_EXPORTED_KEYS
    CUBRID_SCH_CROSS_REFERENCE

    They can be used to get foreign key information. 

2.) cubrid_bind support BLOB and CLOB data types.

3.) cubrid_unbuffered_query now is worthy of its name. It won't need to wait for that all query results have been complete. It will return 
    when the results are being generated, so you can't use cubrid_num_rows() and cubrid_data_seek() on a result set returned from 
    cubrid_unbuffered_query().

4.) cubrid_fetch_object: Add new parameters class_name and params, which can pass the name of class to instantiate and the constructor 
    for class_name objects.

5.) When cubrid_schema() fails, return false instead of -1.
6.) When cubrid_col_size() fails, return false instead of -1.

Fixed bugs:

1.) last db connetion/request resource management: If there is no variable to refer these resources, they will be removed by garbage collector.
2.) cubrid_execute: If cubrid fails to get result info after executing sql statement, there may be memory leak.
3.) cubrid_disconnect: When disconnecting any db connection, it will always reset the last request and connection info.
4.) cubrid_unbuffered_query: When query execution fails, it don't free the allocated request resource.