MySQL BackSlash Encoding ON.

Versions prior to 8.6 of MAGIQ Documents require the "NO_BACKSLASH_ESCAPES" parameter in My.ini for MySQL databases.

Symptoms For MAGIQ Documents versions 8.5.X and prior.

Resolution

Upgrade MAGIQ Documents to latest version using MAGIQ Documents live update tool.

Or if you wish to stay on current release, perform the following:

Change the default "string encoding parameter" in "my.ini" file located in the MySQL installation directory with Notepad.

Add the NO_BACKSLASH_ESCAPES text to the "sql-mode" parameter

Example:

        ... 
        ... 
        # Set the SQL mode to strict
        sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,NO_BACKSLASH_ESCAPES" 
        ... 
        ... 

Save the my.ini file.

Restart the MySQL Service

How to stop and start MySQL from the command line:

        net stop mysql
        net start mysql

Symptoms For MAGIQ Documents 8.6 + servers

MySQL configured prior to version 8.6 may still use the backslash character to escape special characters. This configuration is no longer required and it also causes unwanted results in MAGIQ Documents.

Resolution

Perform the following: Change the default "string encoding parameter", in "my.ini" file located in the MySQL installation directory with notepad.

remove or comment out the NO_BACKSLASH_ESCAPES setting from the "sql-mode" parameter

Example:

        ... 
        ... 
        # Set the SQL mode to strict
        # sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,NO_BACKSLASH_ESCAPES" 
        sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" 
        ... 
        ... 

Save the my.ini file.

Restart the MySQL Service

How to stop and start MySQL from the command line:

    net stop mysql
    net start mysql