Mysql 5 Compatibility
 

MySQL 5.0 and higher have a strict mode that is currenty incompatible with a number of queries in PhotoPost products. The Windows Installer from MySQL.com enables this strict mode by default.

In Layman's terms MySQL in strict mode can not allow query inserts with null values to be entered.

Workaround

There are several workarounds

1. Replace in my.ini the current sql-mode line with sql-mode="MYSQL40"
2. Start MySQL with the option --sql-mode="MYSQL40"
3. Execute the query SET GLOBAL sql_mode='MYSQL40'

MySQL needs to be restarted before changes in my.ini have an effect. My.ini can be found in the MySQL installation directory or the Windows directory, depending on your configuration.

thank you., i was pulling my hair out untill i found this post.

Does the 3rd option set sql mode to MYSQL40 for ONLY the PhotoPost Pro database? I'm considering a purchase, but would like to be able to keep my other databases in MySQL50 native mode. How soon do you expect PhotoPost to be natively compatible with MySQL 5?

That options above set it to backward compatibility with 4.0 and disable the STRICT MODE which is where the incompatibility is. This sets all databases to use the backwards compatibility. There is no date set to when we are going to support mysql 5.

Just to make sure I am understanding this correctly, the STRICT MODE forces the database server to only use MySQL50 functionality?

Also, disabling the strict mode and setting backward compatibility to 4.0 - does this allow the database server to operate in MySQL5.0 mode by default but still allow MySQL4.0 compatibility? Would it be 4.0 functionality by default? Would 5.0 functionality be completely removed?

Trying to determine how other scripts and databases will be affected by changing these settings.

Thanks for your help and quick reply.

I dont think your other scripts would be affected in any way at all.

There should be no issues running mysql 4.0 compatibility mode.

is there problems with running Phoptpost with mysql5? is it easier with mysql?

You can test if you wish we have fixed any issues that have come along so there are no open issues at present