Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
Since cubrid 2008 r3.1 supports BLOB/CLOB type, glo type was removed from engine and from CCI library as well.
However it seems that the following functions, related to glo type, still remained in the PHP codes and I think it will make error messages when user builds php driver.
please remove this from the code, and change documentation at http://kr2.php.net/manual/en/book.cubrid.php
PHP_FE (cubrid_new_glo, NULL)
PHP_FE (cubrid_save_to_glo, NULL)
PHP_FE (cubrid_load_from_glo, NULL)
PHP_FE (cubrid_send_glo, NULL)
In the documentation page of *glo functions on php.net, I have add a note which tells user that these functions have been remove from CUBRID PHP since version 8.3.1.
I think we can still reserve these docs for 8.2.2/8.3.0 users. What do you think?
The actual functions can be removed from the CUBRID 3.1 PHP API. But we have to keep all functions definitions in the PHP.net manual. Like thorny-road said, adding "DEPRECATED" note is fine enough. Users will not have problems as it is documented. But the code should be cleaned for each version.
I'm also fine with adding "DEPRECATED since R3.1 " on each function.
Hi kadishmal, cottonspan:
Should we consider re-organizing the CUBRID PHP APIs or API documentation?
The current CUBRID PHP is designed as the style of extension MySQL. After we have added the CUBRID-MySQL Compatibility functions, the API list becomes much more longer now. Maybe we can learn good idea from Mysqli (MySQL Improved Extension).
They groups their APIs mainly into three categories: MySQLi , MySQLi_STMT and MySQLi_Result, which is more friendly to users.
We can consider this. Perhaps with the new 3.2 PHP API we can reorganize as it will have tons of changes. By that time, please keep considering the possible documentation structure for CUBRID PHP API. We can discuss that later.
I have changed the style of CUBRID PHP Predefined Constant page.