...
- First review Compatibility Guide and Upgrade Planning to check any changing requirements for database versions etc.
- Follow the Standard Upgrade Instructions plus any special instructions for all intermediate releases listed in Compatibility Guide and Upgrade Planning.
Special notes
For this release, there is an additional step when upgrading from a version at less than 7.2.0 to 7.2.0 or above. This only applies if you are running against a SQL Server database.
Change to SQL Server Dialect in datasource file
If you are running against a SQL Sever database, you need to update the dialect specified in the datasource file. The Standard Upgrade Instructions describe managing your phixflow-datasource.xml file, and migrating this to the new release. In this file you will have:
| Code Block | ||
|---|---|---|
| ||
<prop key="hibernate.dialect">org.hibernate.dialect.SQLServerDialect</prop> |
Update this to say:
| Code Block | ||
|---|---|---|
| ||
<prop key="hibernate.dialect">org.hibernate.dialect.SQLServer2012Dialect</prop> |
...
Contents
| Table of Contents | ||
|---|---|---|
|
...
The URLs used to start PhixFlow in standard mode, or to go straight to an application, have changed. See Start PhixFlow on the Client for details.
Performance
Is It is now possible to control some features of Oracle logging from the PhixFlow application.specify on a stream by stream basis
- whether any indices should created during publishing
- whether inserts into Oracle should be direct paths inserts
...
Bug Fixes
Cache refreshes after PhixFlow upgrades
...