First table shows the function in CUBRID and MySQL which have different function names but perform almost same tasks such as cubrid_get_class_name and mysql_tablename. The table also includes the arguments comparison of the functions.
Second table shows the MySQL functions which are absent in CUBRID.
Third table shows the CUBRID functions not present in MySQL.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the research was made to provide better compatibility on php driver between mysql and cubrid. If you see the tables on the link, subtle differences in function name or argument order makes user frustrated. Without thinking of functions which need engine's supporting, php driver itself can be fixed for better compatibility so that user can just change its prefix "mysql_" of each function to "cubrid_".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wrote about the differences between PHP API Functions in CUBRID vs. MySQL based on CUBRID 3.1 Beta. Link : http://cafe.naver.com/studycubrid/769.
First table shows the function in CUBRID and MySQL which have different function names but perform almost same tasks such as cubrid_get_class_name and mysql_tablename. The table also includes the arguments comparison of the functions.
Second table shows the MySQL functions which are absent in CUBRID.
Third table shows the CUBRID functions not present in MySQL.
maybe this case Functions already create new Functions in CUBRID
CUBRID_move_cursor
CUBRID_column_names
CUBRID_column_types
CUBRID_close_request
CUBRID_version
CUBRID_num_cols
reference link : http://dev.naver.com/projects/cubrid/wiki/cubrid-php/CUBRID_PHP_Compare
Hi conpurian,
Thanks for your work. I have already been working on this now. And I will give my response soon.
the research was made to provide better compatibility on php driver between mysql and cubrid. If you see the tables on the link, subtle differences in function name or argument order makes user frustrated. Without thinking of functions which need engine's supporting, php driver itself can be fixed for better compatibility so that user can just change its prefix "mysql_" of each function to "cubrid_".
Hi, I fnd some of MySQL functions which are absent in CUBRID are deprecated. Shall we also implement them? My own opinion is "not". What do you think?
Replicated the same PHP API functions list on CUBRID Global site at http://www.cubrid.org/cubrid_mysql_php_function_comparison. New CUBRID 3.1 PHP functions will be reflected soon.
Hi kadishmal,
CUBRID PHP 3.1 release-notes has been complete. You can read it to get the latest change.
The following functions in "existing only in MySQL" table have been added in cubrid:
cubrid_db_name
cubrid_ping
And cubrid_fetch_object now matches with mysql_fetch_object in CUBRID PHP 3.1
The following functions in "not perfectly match" table also have been added:
cubrid_error
cubrid_errno
cubrid_close
cubrid_query
cubrid_client_encoding
Great! Where can I get that PHP specific release note?
You can get it at sf.net svn:
http://cubridinterface.svn.sourceforge.net/viewvc/cubridinterface/php/branches/RB-8.3.1/
I found that your new PHP Docs update is currently reflected in the temporary PHP.net Docs at http://docs.php.net/manual/en/book.cubrid.php.
I checked that new PHP Docs, and haven't found the new cubrid_lob_close() function documented in there.
I'm afraid that I forgot to add it … I will add it soon.
And I will upload all .so & .dll for CUBRID PHP 3.1 next week as soon as possible.
I have updated the comparison table at http://www.cubrid.org/cubrid_mysql_php_function_comparison.