...
The migration4.0.2_to_4.0.3.sql file includes all of the 403PatchRelease*.sql files in it. Patch Release SQL files are only necessary if you are on a 4.0.3 Patch Release.
If you are upgrading from a 4.0.3 Patch Release, follow the date based SQL files in sequence by Date. If you have already a applied specific Patch Release patch then skip it. You can make determination of which Patch Release files to run by looking at Build Time on the About window of your FlexDeploy installation. After completing the last 403PatchRelease, run the migration4.0.3_to_4.5.0.sql file. Contact Flexagon support for details if you are not sure. See example below.
...
Code Block |
---|
language | sql |
---|
title | Upgrading 4.0.3 (build time 34/823/2017 or earlier) to 4.5.0 |
---|
linenumbers | true |
---|
collapse | true |
---|
|
-- As first patch release 4/24/2017 is after build time, we can just apply entire 4.0.3 to 4.5.0 migration sql
migration4.0.3_to_4.5.0.sql |
Code Block |
---|
language | sql |
---|
title | Upgrading 4.0.3 (build time 4/7/2017) to 4.5.0 |
---|
linenumbers | true |
---|
collapse | true |
---|
|
-- As first patch release 4/24/2017 is after build time, we can just apply entire 4.0.3 to 4.5.0 migration sql
migration4.0.3_to_4.5.0.sql |
Code Block |
---|
language | sql |
---|
title | Upgrading 4.0.3 (build time 4/24/2017) to 4.5.0 |
---|
linenumbers | true |
---|
collapse | true |
---|
|
403PatchRelease_04-24-2017.sql
403PatchRelease_05-01-2017.sql
403PatchRelease_05-5-2017.sql
403PatchRelease_05-11-2017.sql
403PatchRelease_05-22-2017.sql
403PatchRelease_06-14-2017.sql
403PatchRelease_07-19-2017.sql
403PatchRelease_07-24-2017.sql
migration4.0.3_to_4.5.0.sql |
...