27 results found
-
Comparsion options - Ignore INT IDENTITY
When transferring tables, it may happen for various reasons that a column with the data type “int identity” is occupied in the source or DEV system.
It would be nice if the value of the identity could be ignored.
Perhaps an extension of “Ignore identity seed and increment values” would be possible here.1 vote -
Flyway Desktop - Configurable config file location
It would be nice to be able to store the configuration normally in flyway.user.toml in a standard location instead of within the project folder.
Since .user.toml files are ignored by git then they need to be backed up and restored when the project is cloned to another machine (or deleted and re-cloned).
Instead it would be better if user settings where stored somewhere like ~/.flyway (macOS) and $env:APPDATA (Windows) so they can be migrated between machines easier.
1 vote -
Custom Filter Buttons
Currently filters are configured once and tracked in the project. It would be nice to have the ability to create custom filters that can be applied on the Schema model page on-demand to limit what is returned. The idea is that would be temporary overrides that do not get applied by default.
We use a shared database for development and there are often dozens of objects undergoing development. We currently employ a standard object naming convention for these so we can filter them out, but it would be nice to easily toggle these filters to have on-demand control over what…
1 vote -
Make Deployment Script Read-only with Toggle for Edit
I would like to suggest an enhancement to the current functionality where Deployment scripts are displayed in the GUI. Currently, these scripts are editable by default, which can lead to unintended modifications.
I propose displaying the script as read-only by default with a radio button or "edit" option to toggle for editing.
1 vote -
Add an option to ignore the state of triggers during comparison
We have an application that likes to disable and enable triggers during loads so these get in different stages depending on the state of our database. It would be nice to ignore these and not see them as differences when looking or comparing them in Flyway Desktop. We can't exclude them in our database as they are triggers that we need but we really don't need to compare them to source control since we know that one is enabled and the other is disabled its ok for us as the application turns these on and off as necessary.
1 vote -
Support updating the flyway schema model directly
Officially support flyway users updating the schema model directly. You can do this now, but even with identical t-sql in the schema + migration folders, flyway diff can produce false diffs.
This appears to be caused by how redgate scripts out the applied migrations (constraints in a particular order, using <> instead of !=) vs looking at the schema files directly.
I believe this could be resolved by running the schema files through the same scripting method so the end result t-sql syntax is identical.
See support request 340787 for more details.
1 vote -
Flyway Project Dashboard
I have around 20 schemas that I need to check. So I propose a dashboard that we can use to setup the schemas and then initiate a compare for those that we want to check.
This is to replace the functionality of the Source Control for Oracle, that we lost with the Flyway desktop. Having to open each Flyway project separately takes a long time, only to find no changes to the schema.
The Source Control did this all at once when you opened it, it showed all the registered schemas in one big list. It would then go off…
1 vote
- Don't see your idea?