Flyway Desktop 5 release notes
Published 11 October 2021
5.17.1 - Dec 19th, 2022
- Clean no longer runs in a transaction so objects such as memory-optimised tables for SQL Server can now be deleted correctly
- Updated flyway engine to 9.10.1
- Updated SQL Compare engine to version 22.214.171.12484
- Updated Compare for Oracle engine to version 126.96.36.1998
5.17.0 - Dec 9th, 2022
- Projects named using the redgate-change-control project naming convention are no longer automatically converted to flyway-dev
- Automatic setting of the flyway.oracle.sqlplus property in old projects is no longer performed
- Projects containing old style inline connections are no longer
supported - projects should use
- Added support for putting shadow databases on the same database as development for single schema databases by allow editing of shadow schema in the UI
- Schema changes are now handled alongside static data changes (though some schema changes may need to be resolved before static data changes are picked up)
- Updated flyway engine to 9.10.0
- Updated SQL Compare engine to version 188.8.131.5281
- Updated Compare for Oracle engine to version 184.108.40.2067
5.16.17 - Dec 5th, 2022
- Merge conflicts can now be resolved through the version control tab
- We now have preview support for tracking static data for Oracle, by adding the configuration for which tables to track to the flyway-dev.json config file
- It is now possible to run
flyway checkwith the
-codeflag for code analysis on the migrations page (with SQLFluff installed)
- Updated Compare for Oracle engine to version 220.127.116.110
5.16.16 - Dec 1st, 2022
- Fixed issue with static data deployment script contents
- Updated SQL Compare engine to version 18.104.22.16813
5.16.15 - Nov 30th, 2022
- Fixed issue where static data scripts might be generated incorrectly when static data undo scripts are being generated, by disabling static data undo script generation. This feature will be restored in an upcoming release.
- Updated flyway engine to version 9.8.3
- Updated SQL Compare engine to version 22.214.171.12450
- Updated Compare for Oracle engine to version 126.96.36.1997
5.16.14 - Nov 25th, 2022
- We now have preview support for tracking static data for SQL Server, by adding the configuration for which tables to track to the flyway-dev.json config file
- Automatically select the previously executed Flyway command after executing a command and returning to the Migrations tab
5.16.13 - Nov 21st, 2022
- Resolved an issue where checkboxes would display incorrectly when a table was scrollable
5.16.12 - Nov 18th, 2022
- Flyway Desktop will now reload a project if the project’s settings files have changed.
- Fixed issue where link to output report would not work when performing flyway check
5.16.11 - Nov 11th, 2022
- Added previous/next buttons in diff panel
- It is now possible to persist the database used for baselining and to select an existing target database when baselining
- PostgreSQL object-level history and migration generation is now out of preview and generally available
- Added ability to adjust height of diff panel
- Added loading spinner in branch dropdown when checking out
- Branches which are deleted outside of application are now removed from branch dropdown on window focus
- Fixed the development database failing to show in the target databases dropdown (under the migrations tab) under certain conditions
- Fixed branch filter
- Fixed loading spinner in create branch modal
5.16.10 - Oct 31st, 2022
- Fixed credential information not always saving in the connection editor if the credential type changed as a result of pasting in a different url
5.16.9 - Oct 27th, 2022
- Fixed issue where baseline message would not appear when using Oracle
5.16.8 - Oct 26th, 2022
- Now able to open projects from version control
- Fixed scenario that would cause the application to prompt for sign in after offline activation
5.16.7 - Oct 20th, 2022
- By default, only pending migrations are now shown on the migrations tab.
- Long database display names are now truncated in the target databases table
5.16.6 - Oct 11th, 2022
- It is now possible to select the development database from the initial target database dropdown on the manage migrations page
- Improved timeliness of baseline check
- The initial
Add target databasebutton on the manage migrations page now opens a connection dialog directly rather than showing the target databases page
- Fixed a bug where the baseline connection would fail for password authentication types in SQL Server
5.16.5 - Oct 6th, 2022
- Added Manage my licence button to edition selection screen
- Added success status message on the Generate Migrations page
- Added prompt to verify migration following migration generation
- The git branch dropdown will now expand to show longer branch names.
- The generate migrations tab now includes a descriptive header even when there is no connection.
- Changing the file extension when adding a migration now changes the syntax highlighting in the editor.
- Fixed cases where the access token parameter to flyway would not be passed the correct value
- Fixed bug where connection storage type was not pre-selected when switching between authentication types in SQL Server connection dialogs
- Updated Flyway to version 9.4.0
- Updated Schema Compare for Oracle Engine to version 188.8.131.529
- Updated SQL Compare Engine to version 184.108.40.20661
5.16.4 - Sep 30th, 2022
- Headers now include a help tooltip that give more descriptive information about a tab’s purpose.
- Fixed issue where authentication-specific fields were not showing up correctly on switching authentication type in SQL Server connection dialogs
5.16.3 - Sep 29th, 2022
- Fixed an error parsing output of flyway check command
5.16.2 - Sep 27th, 2022
- Added ability to initialize a new repo in version control page.
- Improved resize behavior of icons & text in commit and differences tables.
- Git branches can now be deleted from the branch selector.
- Error banners now include a button to show the full error in a scrollable modal.
- The first versioned migration in a project will now start with
- The migrations table is no longer automatically refreshed on adding a flyway parameter
- Flyway desktop will now clean up previous updates downloaded through check for updates
5.16.1 - Sep 14th, 2022
- Restored the narrower row style in the Migrations table.
- Fixed misaligned version input box
- Fix some styling errors in Migration table.
- Updated Schema Compare for Oracle Engine to version 220.127.116.110
- Updated SQL Compare Engine to version 18.104.22.16878
5.16.0 - Sep 9th, 2022
- Flyway Desktop can now be run in Community edition with a subset of features (preview)
- License key (masked) and edition now show up in flyway command view
- Performance of the version control changes table has now been greatly improved.
- Hovering over migration states provides a description of the state
- The schema model and generate migrations tables have been updated to fit more content.
- Fixed an issue where new projects weren’t being added to the recent projects list.
- Made the migration description field on the Manage migrations page less restrictive, to allow all valid file names
- Fixed error handling when failing to add a new migration so that add migration screen isn’t closed
- Empty connection dialog fields are no longer highlighted on opening connection dialog
- Fixed error handling when “Clean and retry” fails on the generate migrations page
- Importing an existing project will now open it unaltered
- Fixed sorting of the state column in the Migrations table.
- Fixed potential error message overflow for errors displayed via a toast in the bottom right hand corner of the screen
- Updated SQL Compare Engine to version 22.214.171.12462
- Updated Schema Compare for Oracle Engine to version 126.96.36.1994
- Updated Flyway to version 9.2.3
5.15.7 - Aug 31st, 2022
- Fixed an incorrect message when pulling changes from version control.
5.15.6 - Aug 25th, 2022
- Feedback link is now version specific
- Flyway check on the Migrations page now returns a more helpful result if no report type is specified
5.15.5 - Aug 18th, 2022
- It is now possible to choose to save database connections to the project settings (for version control) or user settings
- Improved handling of connection urls in comparison operations.
- Colour of Save button on the “Add migrations” page is now blue
- Target databases will now be combined when specified in both project settings and user settings
- It is now possible to opt out of creating a new folder when creating a new project
- Highlight invalid field if the user tries to add a migration with special characters
- Update Electron to version 20
5.15.4 - Aug 3rd, 2022
- It is now possible to edit the development and shadow database connections from the settings cog
- The Flyway verb is now preserved when refreshing the Manage Migrations page
5.15.3 - Jul 28th, 2022
- It is now possible to run the Check command from the migrations screen
- The shadow database will now be cleaned automatically when a baseline script is deleted and regenerated
- Fixed issue where incorrect target database name could be shown in Manage Migrations page
- Updated Flyway to version 9.0.1
5.15.2 - July 19 2022
- It is now possible to directly select target databases when opening a project with targets configured
- Small UI improvements to Target Databases configuration page
- Commit is no longer disabled when a background fetch is in progress
- Passwords no longer need to be reentered when editing a connection
- Updated SQL Compare Engine to version 188.8.131.5240
- Updated Schema Compare for Oracle Engine to version 184.108.40.2066
220.127.116.11 - July 13 2022
- It is now possible to manually add a migration script on the Migrations page
- The version control page will now refresh if a git repository is initialised outside the toll
- It is now possible to specify username and password in connection dialog for all databases
18.104.22.168 - July 05 2022
- It is now possible to trial Teams edition, though it is not yet
available for purchase. It is possible to switch the edition being
trialed from the
Compare editionsentry in the help menu.
- Fixed script viewer command menu containing some actions which could not be applied
- Fixed dismiss button for the error notifcation being moved by long error titles
- Improved error handling when attempting to view a migration that cannot be read from disk
22.214.171.124 - June 28 2022
- Updated SQL Compare Engine to version 126.96.36.19916
- Updated Schema Compare for Oracle Engine to version 188.8.131.524
184.108.40.206 - June 23 2022
- You can now edit database connections in the Migrations tab without first selecting them.
- Fixed issue connecting using Azure Active Directory Interactive authentication from the database connection dialog
- Fixed issue where the manage migrations table would overflow incorrectly given a large number of migrations
220.127.116.11 - June 21 2022
- Fixed issue parsing comparison options
- Updated Flyway to version 8.5.13
- Updated SQL Compare Engine to version 18.104.22.16846
- Updated Schema Compare for Oracle Engine to version 22.214.171.1245
126.96.36.199 - June 20 2022
- For Oracle projects, it is now possible to specify schemas for the database to baseline against
- For Oracle projects, an error will now be thrown when comparing with an unrecognised schema, instead of treating it as empty
- For new projects flyway.validateMigrationNaming is set to true by
default, validating migration names when
flyway infois run
- Fixed error when settings specified multiple times in flyway.conf
- Fixed error when the same comparison option is specified multiple times
188.8.131.52 - June 14 2022
- Removed misleading message from connection dialogs for databases which only contain a JDBC URL field
- Fixed error which could prevent the install update on exit button from starting the installer
- Fixed error where manually checking for updates could fail when the automatic check was already running
184.108.40.206 - June 08 2022
- Improved error screen when unable to communicate with the Redgate licensing client
220.127.116.11 - May 27 2022
- It is now possible to persist and select target databases from the
- It is now possible to configure a display name for the development database and for the shadow database
- Fixed an issue where it was possible to queue up multiple update installs
18.104.22.168 - May 20 2022
- The target database connection can now be edited on the Migrations page
- For all database types, username and password can be read from jdbc url if pasted in
- For SQL Server, Oracle, and PostgreSQL, there will be a prompt in the connection dialog for username and password if they are required but not supplied
- For SQL Server Azure active directory interactive authentication, tenant IDs and client IDs can be read from the JDBC URL if pasted in
- For SQL Server Azure active directory interactive authentication, there will be a prompt in the connection dialog for tenant ID and client ID if they are not supplied
- For SQL Server the authentication and integratedSecurity parameters will now be correctly parsed from the JDBC URL if pasted in and will be visible in the connection dialog UI (they were previously added programmatically and not displayed)
- For Oracle, LDAP JDBC URLs will now be handled on the Migrations page
- Fixed a broken link to external documentation.
- Fixed an issue that caused parts of the UI to overflow out of the viewport
- Updated Flyway to version 8.5.11
- Updated SQL Compare Engine to version 22.214.171.12428
- Updated Schema Compare for Oracle Engine to version 126.96.36.1990
188.8.131.52 - May 10 2022
- It is now possible to configure undo script generation in the UI
- Fix for git stage operation failing when given a large number of files
184.108.40.206 - May 05 2022
- Improved signing in with your Redgate ID
- Moved the ‘Go to project folder’ and ‘Open in console’ buttons to the tab menu to make closing a project easier
- You can now configure schemas for your target connection in the Migrations page.
- SQL Server connection dialogue now only highlights an empty database field on connection test.
220.127.116.11 - May 03 2022
- Internal fixes and changes
18.104.22.168 - April 20 2022
- Add error message when the installed version of git is unsupported
(the minimum supported version is
22.214.171.124 - April 13 2022
- Fixed bug where an invalid oracle JDBC Url could not be edited using the connection dialog
126.96.36.199 - April 07 2022
- Clicking on migration entries on the Migrations page will always show the versioned migration script by default
- Fixes an issue where certain log levels could cause licensing check failures.
188.8.131.52 - April 05 2022
- The generate migrations page will now refresh automatically following a save to the schema model
- Results screens will be automatically dismissed when navigating away from tabs and performing related operations on other tabs
- For SQL Server projects, the “Database name” field is now required in connection dialogues.
184.108.40.206 - March 30 2022
- Fix incorrect multi-selection behavior on the differences table when a filter is applied
- Fixed an issue where Migrations operations could be called with stale parameters.
220.127.116.11 - March 24 2022
- Make version of Flyway installed with Flyway Desktop accessible through the PATH environment variable.
- Flyway Desktop will now display a small splash screen before it’s finished loading.
- The comparison option
IgnoreSystemNamedConstraintNamesis now overridable by the user, defaulting to
18.104.22.168 - March 22 2022
- The schema model page will now show for all Oracle projects. Oracle migrations are now always generated from the schema model and can no longer be generated directly from the development database.
- Added Flyway parameters are no longer applied to the table on the Manage migrations page
- Fixed an issue where warnings or messages could be output in an incorrect format during comparison
- Fixed an issue that prevented the dry run button from showing on the Manage migrations page
22.214.171.124 - March 15 2022
Flyway Desktop now encrypts SQL Server connections by default when invoking Flyway
For SQL Server users, connections are now set to be encrypted by default.
This will break existing stored SQL Server connections if they rely on encryption being off (the previous default). Flyway Desktop will show an error when attempting to call Flyway that will normally mention a failure to find a valid certificate.
Either one of the following actions can remedy this: * Delete the
flyway-dev.user.json file in your project. Flyway Desktop
will prompt you for new connection details. *
OR * Open
and manually edit the following properties, appending either
;trustServerCertificate=true, taking into account that this
potentially affects the security of your database connections. *
- Objects being included in a baseline migration as dependencies are now declared to the user.
- Generating baselines no longer include default objects as dependencies
126.96.36.199 - March 15 2022
- Prevent the flyway_schema_history table from being shown as dropped when generating migrations in Oracle single schema mode
- Updated Flyway to version 8.5.3
188.8.131.52 - March 11 2022
- Fixed an issue where some actions buttons on the generate migrations tab could be hidden off the page.
184.108.40.206 - March 10 2022
- Added filter box to the Schema model and Generate migration pages
- Long object or schema names will now truncate in the changes table. Hover for tooltip of full name.
- Fixed an issue where exception reporting would happen when it should not
220.127.116.11 - March 07 2022
- Added the option to run different Flyway commands from the manage migrations page
- A schema model folder is no longer created in a new project which does not support schema model behaviour yet
- Fixed an issue with importing flyway.conf for some database types
- Fixed an issue with error message “It is not possible to apply changes directly to your migrations” which might occur if applying after clicking between tabs quickly
- Fixed issue where objects with no schema might be displayed with dbo as the schema
- Fixed issue where dry run script modal would still be open following migrate action
- The target database on the Manage migrations page is now cleared when the project closes
- Fixed SQL Server issue where baseline script might fail to deploy to shadow database because of schemas or roles already existing
- Fixed SQL Server issue where Flyway schema history table could not be created in the shadow database when configured in a custom schema
- Updated Flyway to version 8.5.2
- Updated SQL Compare Engine to version 18.104.22.16856
- Updated Schema Compare for Oracle Engine to version 22.214.171.124
126.96.36.199 - February 28 2022
- Fixed error caused by object definitions over 150,000,000 characters long
188.8.131.52 - February 25 2022
- Fixed an error notification that could occur when closing a project during a comparison.
- Fixed an issue where comparing schema model could fail for certain log levels.
184.108.40.206 - February 23 2022
- Comparisons now have richer progress reporting.
- Added more granular error handling and verbose logging around comparison artifact serialization
- Current log level is now visible via a tick next to the selected log level in the help menu
- Fixed missing check for updates button on the help menu
220.127.116.11 - February 21 2022
- Updated SQL Compare Engine to version 18.104.22.16818
22.214.171.124 - February 17 2022
- Added menu option to open the current project in the console
- Added option to clean the shadow database and rerun comparison following an error comparing migrations
- Pop-ups will no longer appear from actions made by unrelated tabs
- Fixed issue that prevented changes to generated scripts from being saved
126.96.36.199 - February 15 2022
- Added additional logging around database connection resolution
- Baseline scripts are now saved as flyway baseline scripts with a
- New SQL Server projects will default to dbo for creating schema history tables.
- The shadow database will be cleaned if any migrations contain a Failed status
- Fixed possible getStatus errors which might appear in the logs
- Updated Flyway to version 8.5.0
188.8.131.52 - February 09 2022
- Fixed issue where list of recent projects might not update correctly when empty
- Fixed an issue where generated scripts would not be renamed correctly
184.108.40.206 - February 08 2022
- It is now possible to automatically generate undo scripts by setting generateUndoScripts to true in the Deployment section of the flyway-dev.json settings file
- Unexpected flyway errors should not be reported with additional context
- Dependencies included when saving schema changes to project or applying schema changes to the development database are now displayed on operation success
- The View Command window on the Migrations page now shows the database connection properties
- Flyway migrate error messages are now correctly displayed
220.127.116.11- February 03 2022
- It is now possible to view undo scripts from the Migrations page #### Improvements
- Improved error handling when opening an invalid project
- Improved error handling when failing to connect to a database when refreshing on the Schema model or Generate migrations pages
- Database dropdown when creating a new project is now filterable
- List of flyway parameters on the Migrations page is now filterable
- The Generate migrations and Schema model pages are now more consistent in style. #### Fixes
- Fixed error when generating a migration and the migrations folder doesn’t exist
- Fixed issue updating instance name in SQL server connection dialog when instance name appended to host name #### Library Updates
- Updated Flyway to version 8.4.4
- Updated SQL Compare Engine to version 18.104.22.16833
- Updated Schema Compare for Oracle Engine to version 22.214.171.12411
126.96.36.199 - January 27 2022
- Fixed issue where Flyway Desktop would keep prompting for an update.
188.8.131.525 - January 25 2022
- Improved error reporting for errors interacting with the filesystem
- Connection fields now default to highlight the text on selection (excluding the JDBC URL) #### Fixes
- Fixed error when clicking on the baseline entry in the Migrations view #### Library updates
- Updated Flyway to version 8.4.2
- Updated SQL Compare Engine to version 184.108.40.20665
5.11.862 - January 18 2022
- Add Encrypt and TrustServerCertificate checkboxes to the connection dialogs for SQL Server projects
- Updated Schema Compare for Oracle Engine to version 220.127.116.1187
- Updated SQL Compare Engine to version 18.104.22.16818
- Tooltips added to version control buttons when disabled
- Addressed issue Devart.Data.Oracle.dll as there is a bug in version 5.15.1410
5.10.857 - January 12 2022
- Fixes an issue with the application icon not showing
5.9.853 - January 12 2022
- Added the ability to specify custom flyway options on the migrate page
- Updated SQL Compare Engine to version 22.214.171.12400
- Updated Flyway to version 8.4.1
- Updated Schema Compare for Oracle Engine to version 126.96.36.19961
- Fixed an issue where generating a very large migration script might fail
- Fixed an issue for Windows users where an error could be thrown when linking a database on the Migrate page.
- Improved error handling for actions on the Migrations page
5.8.829 - December 21 2021
- Added new Migrations page where you can view migrations and test deployments against databases
- Updated Schema Compare for Oracle Engine to version 188.8.131.5279
- Updated SQL Compare Engine to version 184.108.40.20630
- Fixes link to apply functionality in successful pull message
- Removed preview label from SQL Server
5.7.805 - December 16 2021
- It is now possible to import Flyway Desktop projects from flyway.conf files via the new import button on the landing page.
- Updated Schema Compare for Oracle Engine to version 220.127.116.1168
- Updated SQL Compare Engine to version 18.104.22.16878
- Removed unused secret storage field from baseline database connection dialog
- Improved error messaging if baselining produces no migrations
- When the shadow database is cleaned for SQL Server, objects outside a schema will now be cleaned
- Timestamps added to migration script version numbers are now generated using UTC for better consistency across remote teams
- Fixes schema validation so that a development database cannot be configured without specifying a schema.
- Schemas no longer need to be specified for SQLServer. All schemas
will be included by default and a filter file should be used for
excluding schemas. Note that for this change to properly take effect you
will need to either create a new Flyway Desktop project or update the
flyway.config file in you existing project to include
flyway.createSchemas=falseas well as enabling schemas in the Filter.scpf file.
5.6.794 - December 09 2021
- Updated Schema Compare for Oracle Engine to version 22.214.171.1247
- Updated Flyway to version 8.2.1
- Updated SQL Compare Engine to version 126.96.36.19938
- Initial version migrations now include a timestamped version number.
- Resolved an issue where timestamps in version numbers were not updated for new migrations.
- Fixed recent projects list sometimes failing to load correctly
5.5.759 - December 01 2021
- Updated Schema Compare for Oracle Engine to version 188.8.131.525
- Updated Flyway to version 8.2.0
- Initial version migrations now include a timestamped version number.
- Resolved an issue where timestamps in version numbers were not updated for new migrations.
5.4.756 - November 30 2021
- Updated Flyway to version 8.1.0
- Updated SQL Compare Engine to version 184.108.40.20663
- Updated Schema Compare for Oracle Engine to version 220.127.116.116
- Fixed issue with testing Sql Server integrated auth connections
5.3.751 - November 25 2021
- Updated SQL Compare Engine to version 18.104.22.16846
- Updated Schema Compare for Oracle Engine to version 22.214.171.1242
- Fix comparing the migrations against the schema model causing a clean and rebuild of the shadow database in cases where it isn’t necessary
5.2.747 - November 23 2021
- Updated Schema Compare for Oracle Engine to version 126.96.36.1995
- Updated SQL Compare Engine to version 188.8.131.5238
5.1.716 - November 17 2021
- Updated Schema Compare for Oracle Engine to version 184.108.40.2063
- Updated SQL Compare Engine to version 220.127.116.1121
- Addressed issue parsing some Oracle jdbc urls
- Fixed issue parsing large flyway output when refreshing generate migrations page
5.0.710 - November 11 2021
- Improved error handling for missing flyway.conf
- Updated SQL Compare Engine to version 18.104.22.16807
- Updated Schema Compare for Oracle Engine to version 22.214.171.1243
- Updated Flyway to version 8.0.4
- Improved error handling for Azure Active Directory error handling
- Improved error handling when flyway command line returns a lot of output
- Prevented possibly confusing baseline message when reviewing a newly generated baseline script
5.0.645 - November 08 2021
- Updated SQL Compare Engine to version 126.96.36.19975
- Updated Schema Compare for Oracle Engine to version 188.8.131.525
- Updated Flyway to version 8.0.3
4.11.194 - October 19 2021
- Updated SQL Compare Engine to 184.108.40.20619
- Updated SQL Compare Engine for Oracle to 220.127.116.115
- Improved progress logging for generating migrations
- Fixed issue where some icons were not displayed correctly
4.10.19628 - October 12 2021
For SQL Server, dependencies are no longer pulled in if they are excluded in a filter file
- Updated SQL Compare Engine to 18.104.22.16871
- Updated SQL Compare Engine for Oracle to 22.214.171.1240
- Improved error reporting for flyway errors
- Fixed a possible issue during baseline where an error resulting from being unable to access an artifact folder would be logged
4.9.19399 - October 05 2021
- SqlServer projects now contain a default filter file which ignores users
- Schemas are now ignored by default in the schema model for new SQL Server projects. These are handled natively by flyway.
- flyway.mixed is now set to true by default for new projects.This allows objects which cannot be wrapped in transactions to be handled automatically.
- Updated SQL Compare Engine to 126.96.36.19954
- Updated SQL Compare Engine for Oracle to 188.8.131.524
- Fix an issue where selecting a large number of changes to apply might raise an error during the apply action due to argument length limitations.
- An error is now thrown when refreshing the migrations page and a flyway.conf file is configured but does not exist on disk
4.8.19143 - September 27 2021
- Updated SQL Compare Engine to 184.108.40.20616
4.7.19002 - September 22 2021
- Updated SQL Compare Engine to 220.127.116.1168
- Fixed an issue with whitespace around schema names causing those schemas to be undetected.
4.6.18750 - September 17 2021
- Updated SQL Compare Engine to 18.104.22.16883
4.5.18448 - September 09 2021
- Improved error handling for project file update and secret storage on connection dialogs
4.4.18321 - September 03 2021
- Updated SQL Compare Engine to 22.214.171.12438 #### Changes
- The baseline script can now be edited before saving. #### Fixes
- Fixed JDBC URL validation when fields contain ‘.’ characters
4.3.18078 - August 19 2021
- Updated SQL Compare Engine to 126.96.36.19935 #### New Features
- The database connection dialogues now include more fields to help with populating the JDBC URL.
- The database connection dialogues now include a link to supporting documentation.
4.2.17782 - August 10 2021
- Updated SQL Compare Engine to 188.8.131.5269
- Fixed passing of –no-renames option to git status
4.1.17691 - August 03 2021
- Updated SQL Compare Engine to 184.108.40.20636
- RCC now reads the first location in the flyway.locations property in the Flyway config if more than one are specified. Only the filesystem location is still currently supported.
- Newlines or other whitespace will now be trimmed from connection dialogue fields.
4.0.17611 - July 29 2021
- Introduced a new workflow that lets you develop changes using a schema model and deploy using migrations. This workflow supersedes the old workflow for Source Control for Oracle projects. Existing workflows connecting to a development database are unaffected.
- It is now possible to apply schema model changes to the development database.
- Simplified project creation. Database configuration steps are now prompted on individual tabs.
- Updated SQL Compare Engine to 220.127.116.1131
- Fix issue where artifact zip is overwritten but not truncated
- Fix specifying wrong read request result type
3.51.17066 - July 06 2021
- Updated SQL Compare Engine to 18.104.22.16886
3.50.16868 - June 25 2021
- Updated SQL Compare Engine to 22.214.171.12436
3.49.16461 - June 14 2021
- Updated SQL Compare Engine to 126.96.36.19991
3.48.16378 - June 10 2021
- Updated SQL Compare Engine to 188.8.131.5214
- Fix using tnsnames.ora
- Opening folder links now works as expected
- Use the console for logging under tests. #### Changes
- We now use the default name for the flyway schema history table for new projects instead of setting it to redgate_schema_history
3.47.16195 - June 04 2021
- Updated SQL Compare Engine to 184.108.40.20611
- Reworked credential storage for username/password connections to use Credential manager (windows) or libsecret (linux). PLEASE NOTE: Credentials will need to be re-entered on updating to this version. This is a one-off change.
3.46.15906 - May 25 2021
- Updated SQL Compare Engine to 220.127.116.1140
3.45.15742 - May 19 2021
- Updated SQL Compare Engine to 18.104.22.16886
- We now display the full url rather than a derived name for the development database on the Changes, Generate Migrations, and Apply to Database pages.
3.44.15405 - May 07 2021
- Updated SQL Compare Engine to 22.214.171.12407
3.43.15297 - April 30 2021
- Updated SQL Compare Engine to 126.96.36.19928
- Fixed an issue where RCC couldn’t interpret relative path to scripts folders.
3.42.15070 - April 19 2021
- Fixed an issue where RCC couldn’t connect to SQL server databases using Azure AD interactive authentication.
3.41.15066 - April 19 2021
- The schema model folder is now created on project creation, when specified, so that the link to the folder now opens correctly before a refresh has been performed
- Improved error messages when failing to validate flyway.locations property
- flyway.conf files referenced in the settings which don’t exist are now logged
- Ensured schema filtering is honoured correctly when saving sql server changes to the schema model
3.40.14945 - April 12 2021
- Internal library updates and improvements
3.39.14891 - April 08 2021
- update dependency redgate.oracle.schemacompare.engine to v188.8.131.522
- update dependency org.flywaydb.enterprise:flyway-core to v7.7.2
- Flyway now uses MSAL instead of ADAL for Azure requests.
- Don’t default to the generate migrations tab, to avoid always running a comparison
3.38.14769 - March 30 2021
- Added preview of SQL Server schema model functionality
- Append to existing .gitignore file when importing a Flyway project
- Fixed error on Version Control tab when there is no upstream branch
- Files are staged and committed correctly when the git repository root is not in the project folder
- Fixed version control commit error when given a very large number of files
3.37.14672 - March 23 2021
- Added Azure Active Directory Interactive authentication option for SQL Server.
- Projects are now opened by selecting a project folder instead of a config file. A project folder is any folder that contains either an RCC project settings file or a flyway .conf file.
- Any project that’s opened will generate an RCC project settings file if it didn’t already exist.
- When creating a new project, a project settings folder will be created during the new project wizard.
- Updated dotnet version to 5.0.4.
- Updated redgate.oracle.schemacompare.engine to v184.108.40.2062.
- Updated redgate.sqlcompare.engine to v220.127.116.1117.
- Updated org.flywaydb.enterprise:flyway-core to v7.7.0.
- Fixed issue where RCC could fail to load hybrid-mode projects.
3.36.14334 - March 09 2021
- update dependency org.flywaydb.enterprise:flyway-core to v7.5.4
3.35.14115 - February 18 2021
- No changes to RCC were made in this release.
3.34.14055 - February 12 2021
Use oracle.sqlplus with every Flyway verb that handles checksums.
3.33.13795 - January 27 2021
- update dependency redgate.oracle.schemacompare.engine to v18.104.22.1687
- Ensure save button is not disabled if a versioned migration isn’t present
3.32.13673 - January 19 2021
- update dependency redgate.sqlcompare.engine to v22.214.171.12449
- update dependency redgate.sqldatacompare.engine to v126.96.36.19921
- Fixed an issue where baselining could occur with incomplete information
- Updated links to help documentation
3.31.13574 - January 14 2021
- update dependency redgate.oracle.schemacompare.engine to v188.8.131.527
- update dependency org.flywaydb.enterprise:flyway-core to v7.5.0
3.30.13455 - January 06 2021
- update dependency org.flywaydb.enterprise:flyway-core to v7.4.0
3.29.13396 - January 04 2021
- Add support for tnsnames.ora
- update dependency org.flywaydb.enterprise:flyway-core to v7.3.2
- update redgate.oracle.schemacompare.engine to v184.108.40.2061
- update dependency microsoft.data.sqlclient to v2.1.1
- update dependency devart.data.oracle to v9.14.1160
- Generated repeatable migrations now include SET DEFINE OFF
- Fix repair workflow in GUI and flyway call
3.28.13259 - December 18 2020
- upgrade oracle comparison engine RedGate.Oracle.SchemaCompare.Engine to version 220.127.116.117
- update electron dependency to v9.4.0
3.27.13184 - December 11 2020
- Update dependency redgate.oracle.schemacompare.engine to v18.104.22.1685
3.26.13121 - December 08 2020
- update dependency org.flywaydb.enterprise:flyway-core to v7.3.1
- BREAKING CHANGE - make rcc verbs multi-level
3.25.13028 - December 03 2020
- update dependency org.flywaydb.enterprise:flyway-core to v7.3.0
3.24.12759 - November 18 2020
- Return to a fresh comparison after baselining on the save scripts screen
3.23.12559 - November 12 2020
- Change init options to accept dev url and scripts folder path
- Fixed miscalculated version numbers for migrations immediately after baselines
3.22.12450 - November 10 2020
- Remove the migrations location selector box from the wizard
- Make –migrationsLocation param for rcc init optional
- Display where the project file will be saved in new project wizard
- show correct error message when testing connection
3.21.12110 - November 02 2020
- Users are now prompted for JDBC URLs if any are missing from the project.
- Improvements to error messages when certain required fields are missing.
- Updated Flyway to v7.1.1.
- Upgraded Redgate Oracle Schema Compare engine to v22.214.171.1241.
- Fixed a bug where an error message may not have appeared on the apply to database tab.
3.20.11930 - October 22 2020
repairverb to the cli for repairing the development database schema history table.
versionverb to the cli for getting the current software version of Redgate Change Control and the Flyway engine.
resetverb to the cli to enable management of the shadow scripts folder (an experimental feature).
- Upgraded Redgate Oracle Schema Comparison engine to v126.96.36.1994.
- Fixed a bug where project paths containing spaces were causing errors to be thrown.
3.19.11779 - October 19 2020
- Added new
rcc statuscommand to the command line which throws an exception if there is a validation error.
- Added the next suggested migration script version number to the
- Upgraded Redgate Oracle Schema Compare engine to v188.8.131.525
- Upgraded Flyway to v7.0.4
- Fixed bug where an invalid value
nullwas being passed to schemaVersion when attempting to generate migrations.
- Fixed bug where project validation was incorrectly ignoring future migrations
3.18.11528 - October 09 2020
- Initialize the shadow scripts folder when running
rcc initin compatible projects.
- Upgraded Redgate Schema Comparison engine to v184.108.40.2060
- Fixed an issue where migrating the shadow database would fail if there was a validation error.
3.17.11469 - October 07 2020
- Remove empty repeatable migration scripts instead of adding a comment.
- Upgraded Flyway to v7.0.1
- Upgraded Redgate Schema Compare for Oracle engine to v220.127.116.114
- BREAKING CHANGE - Replaced the
--requestJsonoption for the
rcc initcommand line verb with individual options.
- BREAKING CHANGE - Replaced the
--requestJsonoption for the
rcc updatecommand line verb with individual options.
- Added shorthand to
rcccommand line verbs
3.16.11254 - October 01 2020
- Provides the RCC CLI as a docker image.
- Improved logging when using the RCC CLI.
- Added optional
--formatoption to the RCC CLI verbs. Pass “json” to get machine-readble output.
- Upgraded the Redgate Oracle Schema Comparison engine to v18.104.22.1687
- Fixed an issue where objects being dropped were first being checked for existence.
3.15.11152 - September 25 2020
- Added RCC CLI to environment PATH.
- Upgraded Flyway to v6.5.7
- Fixed an issue where versioned migrations with large numbers in the filename could fail to parse.
3.14.11088 - September 22 2020
- Upgraded Flyway to v6.5.6
- RCC now always uses the inbuilt flyway license key instead of reading it from the config file.
3.13.10951 - September 14 2020
- Fixed an issue preventing the Programmable Object details from being expanded on the save scripts page.
3.12.10833 - September 04 2020
- Added timestamps to the auto-generated version number of new migration scripts.
- Changed the way messages are displayed to the user within the app.
- Upgraded the Redgate Oracle Comparison engine to v5.7.8.
- Fixed an issue where generating a baseline script failed with the error ‘filename or extension is too long’.
3.11.10748 - September 02 2020
- Fixed an issue where the shadow database could not be updated with scripts containing SQL*Plus syntax.
- Fixed an issue where logs were not being correctly handled when applying scripts to the database.
- Fixed an issue where applying scripts failed but was reported as a success.
- Fixed an issue where unstaged files were not being staged before committing.
3.10.10695 - August 28 2020
- When pulling changes, the message to apply changes to database is now shown as an info message and it’s only displayed if you have any pending migrations after the pull.
- Clicking on the apply to database link from the version control tab (after pulling changes) will now also refresh the Apply to database page.
- A link to more help has been added to the repair modal.
- A comparison option file generated by Source Control for Oracle can
now be used in non-hybrid projects (i.e. projects that use a database as
the development source) by including the
ComparisonOptions.xmlfile in the same directory as the
- When only repeatable migrations have been generated the first accordion is expanded by default
- Fixed an issue where applying pending migration would fail if database credentails were stored in the conf file
3.9.10574 - August 25 2020
- Show the number of pending migrations on the apply to database page.
- Improve performance of the New Project Wizard by no longer testing the same connection details multiple times.
- Improve clean up of temporary files.
- Upgraded Flyway to v6.5.5.
- Clarified the wording of the title of the baseline modal.
flyway.outOfOrderby default in new projects.
- Update default comparison options to stop excluding
SET DEFINE OFF.
- Fixed an issue where attempting to commit files staged for deletion would fail.
- Fixed an issue where fetching branches in a repo with no remote would fail.
- Fixed an issue where applying scripts to the database could fail if SQL*Plus specific syntax was used in the script.
3.8.10312 - August 14 2020
- Refreshes the current branch details after pushing commits.
- Improves error messaging if pushing commits fails.
- Trims whitespace from new branch names before attempting to create the branch.
- Automatically focuses to the input field when loading the create new branch modal.
- Pulling changes from git now behaves according to the user-defined global git settings.
- Upgraded flyway to v6.5.4
- Fixed an issue where a versioned script would be created with only a
SET DEFINE OFFstatement.
- Fixed an issue where a versioned script would be created with only a script header comment.
3.7.10074 - August 05 2020
- Fixed an issue that could cause project load errors when using the
redgate.experimental.shadowSchemaproject option when credentials were not present in the project file itself.
3.6.10070 - August 04 2020
- Upgrade flyway to v6.5.3
- Fix an issue that could cause “null password given” errors when using a SOCO dev source.
3.4.9958 - July 27 2020
- The current Flyway version is now shown in the RCC logs and about dialog.
- Upgraded Flyway to v6.5.2
- Downgraded Devart dotConnect for Oracle to v9.11.980 to work around a “Value cannot be null (Parameter ‘hostname’)” error.
3.3.9794 - July 16 2020
- Made the last updated time on the generate migrations tab more user-friendly.
- Upgraded Flyway to v6.5.1.
- Fixed issue where hybrid projects were not using the default comparison options from Source Control for Oracle if no ComparisonOptions.xml exists.
3.2.9527 - July 07 2020
- Automatically detect and apply comparison options set in the linked Source Control for Oracle project when using hybrid mode.
- Automatically clear the commit message after successfully committing changes.
- Upgrade Flyway to v6.5.0.
- Reduced the amount of logging with the default setting.
- Fixed an issue where Redgate Change Control would crash if switching between projects with no migrations present.
3.1.9415 - July 02 2020
- Fixed an issue where RCC would fail to connect to the shadow database
3.0.9366 - June 30 2020
The version control page is no longer an experimental feature and can now be used without setting up an environment variable.
- A warning message is now shown when pulling changes causes a merge conflict, any further actions are disabled until the conflicts have been resolved.
- The commit table now only lists files that are within the project directory (the directory containing the .conf file) or any of its subdirectories
The flyway schema history table and permissions are now properly excluded from the shadow scripts folder.
Fixed an issue where the number of pulled changes were not being reported correclty
Fixed an issue where the selection state in the commit table would reset after refocusing the window.
2.30.9261 - June 25 2020
- Improved error messaging when attempting to commit if no files are selected.
- Improved error messaging for when saving migrations scripts fails.
- Extended integrated Flyway license
- Fixed error when committing if the repository root was not the same as the RCC project root.
- Fixed the rendering of the changes table on the Version Control tab.
2.29.9197 - June 22 2020
- Added a confirmation modal when pushing commits.
- Stop listing remote git branches that have been deleted in the branch-switch dropdown.
- Enable primary actions to be triggered by pressing
- Allow specific files to be selected for committing.
- Upgraded the Redgate Oracle Schema Comparison engine to v22.214.171.12469
- Upgraded Flyway to v6.4.4
- Fixed an issue where the user-defined logging level was being reset to Default when opening the app.
- Fixed an issue where no comparison differences would be shown after deleting local migration scripts from the project.
- Fixed an issue where an error message was being incorrectly displayed during the New Project wizard.
- Fixed an issue where the default placeholder text for the JDBC Url was missing from the baseline setup modal.
2.28.9017 - June 11 2020
- Added a couple of new version control integration features:
- Create new branches
- Switch branches from any tab
- Added description to the pull and push actions
- Improved success message when pulling changes
- Improved the commit pane design
- Improved error messages when using the Version Control tab
- Upgraded the Redgate Oracle Comparison engine to v126.96.36.19929
2.27.8815 - June 05 2020
- Experimental: Version control Redgate Change
Control projects from within the application. This is currently limited
to a few basic git actions (pull, push, commit).
- Pull latest changes from the remote repository
- Commit new migration scripts
- Push new commits to the remote repository
- Improves the information modal shown when editing migration scripts when working with a shadow scripts folder.
- Adds page auto-refresh after performing a
resyncof a shadow scripts folder.
- Improved error messaging throughout the app.
- Upgraded Redgate Oracle comparison engine to v188.8.131.5211
- Upgraded flyway to v6.4.3
- Corrects the wording of the baseline success message
- Fixes an issue where the shadow scripts folder desync success message was not cleared on manually refreshing the page.
- Fixes an issue where updating the shadow scripts folder during a baseline would fail if there were no comparison differences.
- Fixes an issue with broken styling in the New Project wizard.
2.26.8552 - May 28 2020
- Experimental: Use a shadow scripts folder for
generating migration scripts instead of a shadow database.
- Requires the environment variable
SHADOW_SCRIPTS_FOLDERto be set.
- Enable users to
resyncthe shadow scripts folder from the help menu.
- Requires the environment variable
- Improves progress and error messaging in the UI when creating new projects.
- Improves the copy to clipboard button design
- Improves styling of error messages arising from flyway failures
- Removes the introductory page from the New Project wizard.
- Upgrade Redgate Oracle schema comparison engine to v184.108.40.20668
2.25.8163 - May 14 2020
- Improved the types of error messages displayed in the UI.
- Upgraded the Redgate Oracle Comparison engine to v220.127.116.1120
- Upgrade the Redgate SQL Comparison engine to v18.104.22.16827
- Upgrade Flyway to v6.4.2
- Validation errors are now displayed on the generate migrations tab.
2.24.8037 - May 12 2020
- Upgraded the Redgate SQL Server comparison engine to v22.214.171.12486
- Upgraded the Redgate comparison reports generator to v126.96.36.1996
- Paths to Source Control for Oracle projects are now validated in the new project wizard.
- An error is now displayed in the new project wizard if invalid credentials are provided for the baseline target.
2.23.7927 - May 09 2020
- Added a help widget for setting target schemas for hybrid-mode projects in the New Project wizard
- Upgraded the Redgate Oracle Comparison engine to v188.8.131.5283
2.22.7845 - May 06 2020
- Improved error reporting during saving migration scripts.
- Upgraded the Redgate Oracle Comparison engine to v184.108.40.20680
- Migration scripts can now be saved in Hybrid mode.
2.21.7806 - May 05 2020
- Baselining is no longer required for unsupported database types.
- Some log messages have had their formatting improved.
- UI improvements have been made to the test connection button in the new project wizard.
- Migrations are no longer marked as pending in Hybrid mode projects.
- The generate scripts page is now disabled for unsupported database types.
2.20.7737 - May 03 2020
- Upgraded the Redgate Oracle Comparison engine to v220.127.116.1174
- Fixed an issue where a prompt to baseline the project wrongly when using hybrid mode
2.19.7543 - April 28 2020
- Errors are now reported after managing credentials.
- Upgraded the Oracle comparison engine to v18.104.22.16827
- Fixed an issue where baselining could cause an ENAMETOOLONG error.
2.18.7333 - April 22 2020
- Upgrade Flyway to v6.4.0
- Errors when saving migration scripts are now shown in the UI
2.17.7297 - April 20 2020
You can now use Source Control for Oracle filter files to filter out database objects.
How to use:
To use filters with RCC you will have to first generate a filters file using Source Control for Oracle. See https://documentation.red-gate.com/soco5/using-source-control-for-oracle/using-filters.
Once you have a filters file:
make sure you copy and paste the file to the root of your project (i.e. the same level as your .conf file).
go to your .conf file and add
2.16.7261 - April 20 2020
You can now use Schema Compare for Oracle ignore rules to filter database objects.
How to use:
To use ignore rules with RCC you will have to first generate an ignore rules file using Schema Compare for Oracle. See https://documentation.red-gate.com/sco5/setting-up-the-comparison/using-ignore-rules.
Once you have an ignore rules file:
- make sure you copy and paste the file to the root of your project (i.e. the same level as your .conf file).
./<ignore rules fileName>
- Fixed an issue where a baseline error was displayed after clicking the “skip and create” button in the New Project Wizard.
2.15.7155 - April 16 2020
- The Help menu now contains a
Manage My Licenseoption on Windows installations.
- No longer require .Net Framework 4.7.2 for installation.
2.14.7016 - April 11 2020
- Improved the validation of the user-provided settings when creating a baseline
- Improved validation checks of connection details provided during the New Project wizard
- Enabled database baselining when working with hybrid projects
- Upgraded the Schema Compare for Oracle to v22.214.171.12492
- Upgraded Flyway to v6.3.3
- Changed the default tab to be
- No longer allow progression through the New Project wizard with invalid connection details
- Fixed an issue where warnings were not displayed in the New Project wizard when returning to a previously visited step
2.13.6826 - April 6 2020
- Added a help popup for setting the schema on the Development Source page in the New Project wizard.
- Show better errors when opening invalid projects.
- Upgraded the Oracle comparison engine to v5.7.2870
- Improved the error messages shown when performing a baseline fails.
- Fixed an issue where users were prompted to enter shadow database credentials when no shadow database was configured.
2.12.6622 - March 31 2020
- Upgrade Oracle Schema Comparison engine to v126.96.36.19941.
- Upgrade Flyway to v6.3.2.
- Clarify the descriptive text on the Generate Migrations summary page.
- Use the Source Control for Oracle logo on the development source page in the New Project wizard.
- Correctly ship all third-party licenses including the Oracle FUTC.
- A missing schema is now considered to be empty when performing a comparison.
2.11.6390 - March 23 2020
- Enabled projects with no shadow database connection set up to be opened without throwing an error.
- Added a Learn More link to the development source set up page in the New Project wizard.
- Updated the Oracle Schema Compare Engine to v188.8.131.5212.
2.10.6230 - March 13 2020
- Using Source Control for Oracle as a development source is no longer an experimental feature.
- Redesigned the New Project wizard to enable creation of projects using the hybrid mode (i.e. Source Control for Oracle as development source).
- Add warning messages to the UI when resolving project parameters goes wrong.
- DEPRECATED: The
Redgate.experimental.scriptsSourceis now deprecated in favour of
Redgate Oracle Schema Compare Engineto
Flyway by Redgateto
- Fixed an issue where the
rcc-author.exefile had the incorrect copyright details.
- Ignore permission differences when generating migration scripts in hybrid mode.
- Fixed the
afterMigrate__fix_invalid_objects.sqlscript to enable it to comply with the default Code Analysis for Oracle rules used by Redgate Change Automation.
2.9.5930 - March 5 2020
- Renamed the
DEVELOPMENT DATABASEtab to
- No longer incorrectly report the creation of a migration script when no script was created.
- Fixed an issue where generated Repeatable Migration scripts were incorrectly displayed as empty.
- Fixed an issue where the previously opened projects list was being cleared.
2.8.5753 - March 2 2020
- Started ignoring
redgate_schema_historytable indexes when generating comparison differences.
- Fixed an issue where objects that are depended upon by changed objects were incorrectly automatically included in migration scripts
2.7.5655 - February 26 2020
- Fixed an issue where objects belonging to the schema history table would appear in the difference table
2.6.5603 - February 21 2020
- Fixed an issue which could reset recently opened projects list.
- Updated Flyway to v6.2.4
- Fixes an issue where Flyway could crash if the schema history table was in an unexpected state.
- Oracle SQL*Plus parsing extended to support
2.5.5397 - February 18 2020
- Added ability to enable verbose logging via help dropdown.
- General error handling improvements / fixes.
- Ensure all Redgate CLIs are appropriately signed.
- Fixed an issue where loading project failed due to a missing config.
- updated Flyway to v6.2.3
- Includes fix for https://github.com/flyway/flyway/issues/2669.
- update dependency redgate.oracle.schemacompare.engine to v184.108.40.20668
2.4.4938 - February 05 2020
- Updated dependency redgate.oracle.schemacompare.engine to v220.127.116.1130.
- General error handling improvements / fixes.
- Avoid cases where RCC crashed with a white screen.
- Provides additional information in some cases when Flyway failed.
2.3.4166 - January 14 2020
- The difference table’s UI performance has been improved.
- A better error is displayed when an invalid path is given to the New Project Wizard
- The auto-generated
afterMigrate.sqlfile has now been renamed to
- Fixed an issue where the Apply to database tab’s content was not updated after a baseline completes
- Completing a basline successfully now displays the correct success message
- Fixed an issue where the list of added dependencies, in the script generation tab, was being reported incorrectly
- Fixed an issue where we were not accepting underscores in the hostname part of a JDBC URL
2.2.3902 - December 19 2019
- Improved error handling when oracle jdbc drivers are missing from the flyway installation.
- Improved error message when schemas are missing from the dev or shadow databases.
- The default baseline version is now “001” instead of “0.1”.
- Improved the layout of the baseline page.
- The “last updated” / “new changes” messages on the “Generate migrations” tab have been improved to be clearer and more visible.
- Fixed an issue which prevented the baseline suggestion message from appearing on the “Apply to database” tab.
- Automatically generated versions will now preserve leading zeros from the previous version.
- Fixed an issue where a v2 Deployment Suite for Oracle license key would not correctly activate a v2.1 installation.
2.1.3732 - December 13 2019
- Checking for updates to the tool can now be triggered manually from
- Log files for the tool can now be reached through the
- Credentials entered in the New project wizard are now encrypted
instead of written to the
Test connectionbuttons in the
New projectwizard now check all the necessary fields are completed.
- Improve the content and location of baseline messages
- The parameters
Schemasare now required in the
Show files on diskbuttons have been removed and replaced with clickable folder paths in the header bar.
- Fixed an issue in hybrid mode where the path to the scripts source was being incorrectly resolved.
- Fixed an issue where the table of migrations on the
Apply to databasepage was sorting incorrectly.
2.0.3671 - December 10 2019
Redgate Change Control is no longer marked as a beta, and now uses full RG licensing. A new trial should be started: if you need any assistance then get in touch.
redgate.experimental.scriptsSourceis specified, the product will now check for a
DatabaseInformation.xmlfile in the specified location. This helps ensure a correct scripts folder is specified.
- Handy “Show files on disk” buttons have been added in various places to the UI.
- The column headers in the comparison results table have been renamed to match SQL Change Automation.
- The credentials page wording has been updated to specify dev and shadow databases.
- Fixed an issue where a failure in the script generation step didn’t have a way to get back to the comparison.
- If the
flyway baselinestep fails, the generated baseline script will no longer be left behind.
- Empty baseline scripts will now be saved if necessary.
- Any errors while saving generated migration scripts to disk will now be correctly displayed in the UI.
- Fixed an issue where stale results would occasionally be shown in the comparison results diff viewer.
- Running comparison operations are now fully cancelled when new migration scripts are applied to the database.
- The flyway schema history table is now filtered out of the recent changes notification check.
- We’ve identified a possible issue when upgrading from RCC 1.3 or
earlier where the comparison may fail with a
Could not load assembly Newtonsoft.Jsonerror. If this occurs, then uninstalling and reinstalling RCC will fix the issue.
1.6.3492 - December 04 2019
- We now provide a UI for creating an initial baseline script in the wizard and on the “Generate migrations” tab for existing empty projects.
- The table in the “Apply to database” tab now allows sorting on all columns.
- The “Apply to database” tab now has a new column which shows the order the scripts will be run in.
- The database change notification now works in scripts source mode.
- The default flyway table name for new projects is now “redgate_schema_history”.
- Quote marks are now stripped from repeatable migration file names. This fixes an issue where repeatable migrations for programmable objects would not be saved correctly.
1.5.3350 - November 26 2019
- Scripts source mode and single shadow schema mode can now be used together.
To enable scripts source mode, specify
redgate.experimental.scriptsSource=<path to scripts folder>.
There is no longer a need to remove the
redgate.experimental.scriptsSource will take
precedence if set. To enable single shadow schema mode, specify
redgate.shadowUrl must be set
redgate.shadowUrl will take precedence.
- The comparison no longer refreshes automatically in the background.
*is displayed on the refresh button if there are new changes to the development database when require a refresh to identify.
- Changes to user privileges are now ignored.
redgate.experimental.scriptsSourceconfiguration parameter can now be a relative path.
- Updates the displayed icons when in scripts source mode.
- A message suggesting the database be baselined is shown when given a project with no existing migrations.
- Fixed an issue where the tool attempted to validate the source database when in scripts source mode.
- Fixed an issue where details of a validation failure would not be displayed when in scripts source mode.
- Fixed an issue where an additional menu bar was shown in the application.
1.4.3214 - November 20 2019
We’ve introduced a new experimental “scripts source” mode which may reduce how often a shadow database is required.
The scripts source acts as an alternative to the development database and is a directory on disk that contains the SQL script files that represent your database. These scripts can be generated and maintained using Source Control for Oracle and can also be source-controlled.
When in this mode, Redgate Change Control will help you generate migrations scripts from changes that have been pushed to your scripts folder rather than directly from changes made to your database. Depending on your setup, this might mean that fewer people ever need to have access to a shadow database.
Additionally, the shadow database will need to be accessed only to generate migration scripts - you can make changes to your database, save them and source-control without any need for a shadow.
How to use:
To enable this mode in a project, remove or comment out the
flyway.url setting and specify
redgate.experimental.scriptsSource=<path to scripts folder>.
Once enabled, use Source Control for Oracle to manage the scripts folder while making changes to your database. You can then use Redgate Change Control to generate migration scripts from the scripts folder.
It is worth noting that at this stage, this mode cannot be used in conjunction with the experimental “Single Schema” mode introduced in the previous release. We anticipate that these two modes will likely work together in a future release.
- Improved validation messages when loading projects
- Added a help widget explaining programmable objects
- The app now shows a validation error and prevents new scripts from being generated if flyway detects a validation problem (eg applied scripts not resolved in project files)
1.3.3074 - November 11 2019
We’ve introduced a new experimental “single schema” mode which may replace the need for a separate shadow database in some cases:
As the name suggests, this mode only works when the flyway project
covers a single schema. A second schema is required to act as the shadow
when generating migration scripts. To enable this mode in a project,
remove or comment out the
redgate.shadowUrl setting and
There are a couple of caveats when writing migration scripts in this mode:
- Any references to objects in the managed schema must not be schema-qualified. Since the migration scripts will run against different schemas with different names, managed objects must always be created in the current default schema.
- Any references to objects in other schemas must still be schema-qualified. You’ll be responsible for making sure any dependencies of the managed schema are present in the database as appropriate.
CREATE TABLE log ( message VARCHAR2(50), timestamp INTEGER ); -- this object references log in the same schema, so log must not be schema-qualified CREATE OR REPLACE TRIGGER SetTimestampForLog BEFORE INSERT ON log FOR EACH ROW DECLARE v_today DATE; BEGIN SELECT CURRENT_DATE INTO v_today FROM DUAL; -- date2epoch is in a different schema, so must be schema-qualified :new.timestamp := util.date2epoch(v_today); END;
We’re looking into other alternatives around reducing the need for a shadow database, so stay tuned!
- Improved handing of dependencies between stateful and programmable objects in the generated migrations
- Spaces are now allowed in the migration file name when editing generated scripts
- Fixed an issue which would delay the comparison results being displayed while column ordering preferences were being loaded.
- Fixed an issue were selecting changes in the comparison results would set focus to the first change in the list
1.2.2861 - October 31st 2019
- Persist the sort order of the comparison differences table across page reloads and application restarts.
- Added logging to help debug errors loading project settings.
- Fixed an issue where the database name was not being shown in the
header bar when connecting with a JDBC url without
//before the hostname.
- Fixed an issue where the application would sometimes render a blank screen on error.
- Fixed an issue where the UI would occasionally freeze.
- Fixed an issue where the Apply to Database button was not disabled when there was a project validation error.
1.1.2816 - October 29th 2019
- Prevent sorting of the comparison differences table by the checkbox column.
- Improve the UX for displaying unhandled errors.
- Prevent the resetting of comparison difference selections after the page refreshes.
- Automatically trigger a refresh of the database comparison after successfully applying migrations.
- Now displays a repair banner if validating the project fails.
- Folders created on disk for Repeatable Migrations are now pluralised.
- Fixed an issue where attempting to update the product after closing the application sometimes failed.
- Fixed an issue where a valid Oracle JDBC (version 19.3) connection string was not correctly parsed.
- Fixes an issue where the number of comparison differences displayed in the header bar after generating scripts was incorrect.
- Fixed an issue where an error would occur if the repair banner was shown but there were no failed migrations.
- Fixed an issue where script properties were being written to the log file.
- Fixed an issue where writing to the log file errored unexpectedly.
- Fixed an issue where duplicate error boxes could be shown.
- Fixed an issue where incorrect credentials were used to connect to the shadow database.
- Fixed a UI issue where the progress bar was incorrectly displayed.
1.0.2702 - October 23rd 2019
- Now using Flyway 6.0.7.
- Now displays a better error when trying to save migrations into a folder that doesn’t exist.
- Improve messaging when applying to database fails.
- Improve messaging when Flyway project is invalid.
- Fixed an issue where an “object destroyed” error could be shown during shutdown.
- Fixed an issue where the package and the package body could be generated as two repeatable migrations with the same file name.
- Fixed an issue where you would be shown an update notification despite being on the latest version.
- Fixed an issue where cancelling project load cleared list of recently opened projects.
- Fixed an issue where the an update would not start correctly when the app exited.
0.12.2511 - October 16th 2019
- Now using Flyway 6.0.6
- Repeatable migrations for programmable objects will now be emptied when the object is dropped.
- Views and materialized views are now considered as programmable objects.
- Fixed an issue where the password field in the shadow database step of the New Project wizard was not being correctly displayed as a password field.
- Made several stability improvements to the “Generate migrations” and “Apply to database” workflows to fix some race conditions that could leave the UI in an invalid state.
- Fixed an issue where the recently opened projects list could become empty when a project failed to load.
0.11.2335 - October 8th 2019
- Improve performance when the project has a large number of migrations
- Generated scripts default file name no longer contains a timestamp
0.10.2237 - October 3rd 2019
- Added a workflow for repairing a failure when applying migrations to the database
- The progress bar shown when running a comparison is now more accurate
- Improved the performance of the comparison
- Added an introductory page to the New project wizard
- Improved messaging and other UI elements
- The time since the last refresh of the compare data is now shown
- Fixed an issue where a historic message was being shown by mistake
- Fixed an issue where the recently opened projects list was incorrectly populated
0.9.2173 - September 30th, 2019
- Each new version of the Beta will now stop working after 30 days. A warning banner will be displayed when there is less than 7 days left to expire.
- Fixed an issue where if a comparison failed, the full error message would not be shown
0.8.2154 - September 27th, 2019
- Added a button for giving quick feedback
- Uninstalling the product now triggers the Redgate bulk uninstaller, where you can uninstall multiple Redgate products at the same time.
- The “Test connection” button in the New project wizard now displays more error details in a tooltip when necessary.
- Switching away from the Generate Migrations tab no longer forgets the last comparison
- Comparisons are now ran in the background periodically, reducing the need to refresh
- The Generate Migrations tab now shows when the comparison was last updated
- The project description now shows the database name along with the schema instead of the full connection string
- Running a comparison now shows a progress bar instead of an indeterminate indicator
- Improved the UI
- The Migrations tab has been merged into the Apply to Database tab. You can now switch between showing all migrations or only pending migrations by using a dropdown
- The summary page for applied migrations only shows the migrations that were applied, not all
- The migrations table is now ordered with the most recent being displayed at the top
- ProjectDescription direction now matches difference viewer orientation
- Fixed an issue in the New Project wizard where if the migrations folder was requested to be set to a path other than the default, the migrations folder would not be created
- Fixed an issue in the New Project wizard where flyway.locations was being set to an empty string if both the migrations folder and project location was the same
- Fixed an issue where connecting to an Oracle database with username “sys as sysdba” would result in an error when generating migrations
0.7.1932 - September 12th, 2019
- Added a button to error boxes for submitting feedback to Support
- Added a test connection button to the New Project wizard
- Streamlined the New Project wizard
- Fixed an issue where if a programmable object was created but no non-programmable changes were made, the summary page was reporting the creation of a new versioned migration script (even though this file wasn’t actually being created).
- Fixed an issue when saving a migration script would result in an error on Oracle versions 10.1 to 12.1
- Fixed an issue where the shadow database was not being updated when the schema versions were the same but programmable objects needed to be applied
0.6.1830 - September 5th, 2019
- On Windows you will get a notification about future releases, with an option to Install on Exit
- A link to product documentation and contact support is available through a new ‘Help’ menu
- When saving Programmable objects (functions, packages, package bodies, triggers, and types), they are now grouped into folders by type
- Stop the entire page from scrolling when contents overflow
- The header of the migrations table is now sticky
- Project description is now fixed to the top and does not scroll
- The list of programmable objects can now be expanded and collapsed individually
- Added validation for the description field when creating a new migration
- Added borders to script boxes
- The default generated description will now be in the format
- When generating scripts, drops and creates for “programmable objects” are now only written into the relevant repeatable migration and not added to the versioned migration.
- Fixed an issue where the script editor would not shrink once resized
- Fixed an issue where removing the content of a script when editing would result in an error
0.5.1729 - September 2nd, 2019
- Store usernames and encrypted passwords outside of the conf file if they are not provided in there
- Flyway info results are now cached between the “Apply to database” and “Migrations” tabs
- Pending migrations are no longer filtered from the “Migrations” tab
- More object types (functions, packages, package bodies, triggers and types) are now considered “Programmable objects” in addition to procedures.
- Added a cancel button to the request credentials page
- Use the OS user’s username as the migration description instead of ‘generated’
- The migration script viewer, diff and editor components have been improved by using the Monaco editor
- Handle the correct error type on saving migrations
- Upgrades flyway to v6.0.1:
- This should fix an issue where
'eName' is not recognized as an internal or external command, operable program or batch file.would appear in the flyway output erroneously.
- This should fix an issue where
0.4.1597 - August 28th, 2019
- Redgate Change Control now supports Oracle versions below 12.2 by default.
- “Adding a Flyway license key” step has been removed from the wizard.
- No longer requires the FLYWAY_EDITION environment variable
- Added version to title bar
- Show more useful errors in the error title
- Fixed an issue where saving a migration script would result in an error if you had configured Flyway with a license key to use the enterprise edition
- Remove duplicate repeatable objects appearing in the summary
- Stop sorting the diff table when checking the box on a row
- Make script box scrollable
- Selected buttons in the header bar no longer appear to cut off
- Align scripts to top of segment
- Handle errors on saving migrations
0.3.1573 - August 27th, 2019
- Added a new step to the New Project wizard that allows adding a Flyway license key
- You can now click on the product logo (top-left) to take you back to the landing page
- Error messages can now be copied to the clipboard
- Improved error message for an unsupported
- The generated versioned migration script now opens by default
- Fixed an issue where you could not create a new project unless you had changed the location input field
- The migrations table no longer tries to render script contents for non-migration scripts
- Fixed an issue where the apply to database summary was incorrect if a migration could not be applied because a flyway baseline was required
0.2.1442 - August 21st, 2019
- New landing page for opening new or recent flyway projects
- New wizard to assist with creating flyway projects
- New windows installer
- Error boxes can now be expanded to see the details
- Fixed an issue where script differences were being incorrectly rendered
- Fixed an issue where underscores were not allowed in migration script version numbers
- Fixed an issue where an error would be incorrectly displayed if a repeatable migration was superseded
- You’ll now need to copy the oracle driver jars into
C:\Program Files\Red Gate\Redgate Change Control\flyway\drivers. We’re hoping that we’ll be able to redistribute these files at some point, but don’t have a definitive answer yet.
- Added validation on migration script version number
- Added a summary page to show successfully generated migrations
- Added a new Apply to database tab
- Added the ability to cancel a comparison
- Added some UI to explain ignored and out of order migrations
- More detailed error messages
- Improved difference viewer layout when generating migrations
- Improved script and migration name editing experience
- Improved app layout scaling with small screen sizes
- Fixed an issue where the next version number could be generated incorrectly
- Fixed an issue where Oracle packages and package bodies could not be selected separately
- Fixed an issue where extra changes would be shown in the generate migrations tab due to the shadow database being migrated to the wrong version
- You are no longer able to generate scripts if you have pending migrations
0.1.959 - July 24th, 2019
- Add Select All button for selecting changes to include in the next migration scripts.
- Improve the formatting of the SQL Diff viewer
- Downgrade the Java requirement from 12 to 8
0.1.794 - July 18th, 2019
- Provide a GUI for authoring Oracle migration scripts.
- Enable selection of a Flyway configuration for an Oracle project.
- Added a page to display the current state of existing migration scripts.
- Provided a preview of the contents of existing migration scripts.
- Enabled pending migration scripts to be applied to a database.
Generate Next Migration
- Added a page to enable generation of the next migration scripts.
- Added programmable objects.
- Provided a preview of the SQL for changes that could be included in the next migration scripts.
- Enabled selection of changes to include in the next migration scripts.
- Enabled migration script editing and renaming prior to saving.
- Marks generated migration scripts as deployed on save.