CUBRID MySQL Compatibility Interface Code
Brought to you by:
cubrid-guy
| File | Date | Author | Commit |
|---|---|---|---|
| test | 2011-03-08 | cubrid-guy | [r1] First SVN version |
| cubrid_mysql_php_compat_interface.php | 2011-03-08 | cubrid-guy | [r1] First SVN version |
| cubrid_mysql_sql_compat_interface.php | 2011-03-08 | cubrid-guy | [r1] First SVN version |
| license.txt | 2011-03-08 | cubrid-guy | [r1] First SVN version |
| readme.txt | 2011-03-08 | cubrid-guy | [r1] First SVN version |
The current CUBRID PHP Connector is different from the one existing for MySQL:
* The names of the functions might be different ("mysql_query" vs. "cubrid_execute")
* The order of the arguments might be different ("mysql_connect")
* Sometime there is no corresponding functionality between MySQL and CUBRID ("mysql_insert_id", for example)
For the complete list of PHP API functions comparison,
see http://www.cubrid.org/cubrid_mysql_php_function_comparison.
This makes difficult for developers to port application from MySQL to CUBRID,
as many times there is no direct mapping.
Therefore, we have developed this CUBRID MySQL PHP Compatibility Interface,
which acts as a intermediate layer between CUBRID and MySQL, and simplifies the migration process.
The main idea behind the development of this library was to make conversion from MySQL to CUBRID
as simple as just adding a prefix (“cubrid_”) to the existing PHP MySQL function names.
For example, instead of converting:
mysql_query ($sql, $conn)
to
cubrid_execute($conn, $sql)
the developer will just write:
cubrid_mysql_query ($sql, $conn)