Skip to content

Flyway

Flyway

Categories

JUMP TO ANOTHER FORUM

25 results found

  1. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Desktop  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Desktop  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Desktop  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
2 Next →
  • Don't see your idea?