Data type mappings   The types of columns must map correctly between your consolidated and remote databases. For details, see MySQL data mapping.

Storage Engine   The MobiLink server requires the default storage engine to be ACID compliant. If the default storage engine is not ACID compliant, make sure that all MobiLink server tables are created using an ACID compliant storage engine, such as InnoDB and Falcon.

Stored Procedures   You cannot use INOUT or OUT parameters in stored procedure calls. Procedures that require these parameters must be implemented as functions that return an OUT value.

Server events that require INOUT parameters, such as authenticate_user and modify_user, must be implemented as functions and run using a SELECT statement instead of a CALL statement.

Named parameters   User-defined named parameters are not supported.

Cursor Scripts   The events upload_fetch, download_cursor, and download_delete_cursor must be called using a SELECT statement, which the MobiLink server runs using a read-committed isolation level. A bug in the MySQL ODBC driver causes the server to read uncommitted operations, such as INSERT, UPDATE, and DELETE statements, which results in inconsistent data between the consolidated database and the remote database.

To work around this problem, affix a LOCK IN SHARE MODE clause to your SELECT statements. For example,

SELECT column1 FROM table1 WHERE id > 0 LOCK IN SHARE MODE

This clause protects the SELECT statement from uncommitted operations.

Bulk upload   The MySQL ODBC driver does not currently support bulk upload.

MLSD   The MySQL ODBC driver does not currently support MSDTC, so a separate MLSD is not supported.

SQLLEN Datatypes on the 64-bit MobiLink server for Unix   The MySQL ODBC driver defines SQLLEN as a 32-bit integer, causing a discrepancy with the 64-bit MobiLink server, which defines SQLLEN as a 64-bit integer by default. If you are running MobiLink on a 64-bit Unix environment, you must add the following to your ODBC configuration file,

length32=1

This entry forces the server to read SQLLEN as a 32-bit integer. Your configuration should look similar to the following example,

[a_mysql_dsn]
Driver=full_path/libmyodbc5.so
server=host_name
uid=user_name
pwd=user_password
database=database_name
length32=1

MySQL Server Configuration   The MobiLink synchronization scripts are stored in the ml_script table as TEXT and are retrieved when needed. You may need to set max_allowed_packet equal to 16m or greater in the my.ini file.

Conflict detection   The scripts generated for conflict resolution with a MySQL consolidated database have multiple statements. If you are using conflict detection, you must enable the Allow Multiple Statements checkbox on the Flags 3 page of the MySQL Connector/ODBC Data Source Configuration window when you configure a DSN for the MobiLink server to make connections to your MySQL database.

Multiple statements   If any of your synchronization scripts contain batched SQL commands separated by semicolons, you may need to select the Allow Multiple Statements checkbox on the Flags 3 page of the MySQL Connector/ODBC Data Source Configuration window when you configure a DSN for the MobiLink server to make connections to your MySQL database.