Identity Manager now supports MySQL 5.0.60 SP1 Enterprise Server as a production repository. (ID-17735, ID-19703)
You can now use MySQL 5.1.30 Enterprise Server as your Identity Manager production repository, but you might need to change to your my.cnf file. Due to recent changes in MySQL's InnoDB code, the default binary logging format is now STATEMENT. Identity Manager uses a READ-COMMITTED transaction isolation level, so binary logging in STATEMENT mode produces an error similar to the following: (ID-20460).
com.waveset.util.IOException: java.sql.SQLException: Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT' |
If you enable binary logging, set the mode to MIXED by adding the following line to your my.cnf file:
binlog_format=mixed |
With this configuration change, you can use 5.1.30 as your repository without the binary logging exception. For more details, see MySQL bug #40360.
The Identity Manager Repository has been changed to work around MySQL defect 9021. The Repository's MysqlDataStore now generates a separate, named JOIN for each attribute condition. (Previously, the MysqlDataStore in some cases used SUBSELECTs and the EXISTS predicate.) (ID-15636)
The usage output for the setRepo command has been updated. The usage now lists -o as an option and explains that -o causes setRepo not to perform an initialization check on the new repository location. The usage also now shows the -U and -P flags in examples of direct JDBC connections. (ID-19475)