Flyway Deskop Removes DefaultCollation in RedGateDatabaseInfo.xml

• 
  Hello fwin,
  
  While it is intentional (a consequence of the underlying comparison engine) it is something we are looking to change as it can be confusing or misleading. Such as in the scenario where multiple developers are committing with very slightly different versions of db.
  
  I'll add your experience to the existing task for this.
  
  May I ask why you needed to add it manually? I'd expect it to be dynamically populated from source.

  Peter_Laws September 09, 2022 12:08

  - 0 +
• 
  Hi!

  
  

  Thank you for your answer. We are currently only using Flyway Desktop as a replacement for SQL Source Control, which means that we are still relying on a state-based model. In our scenario the SqlChangeAutomation Powershell module still needs the collation configuration to properly work.
  

  fwin September 12, 2022 04:09

  - 0 +
• 
  Oh interesting!
  
  Noted, thanks, I've mentally shifted gears; in which case by default Flyway Desktop ignores collations differences (as defined here) please could you check your SQL Change automation project for the corresponding 'SyncOptionIgnoreCollations' project definition?
  
  If the input is consistently the correct collation the easiest remediation for the moment may simply be to ignore.

  Peter_Laws September 13, 2022 12:54

  - 0 +
• 
  We are using the Change Automation PowerShell module, so we don't have have a project definition since we are just using the schema-model which was created by Flyway Desktop.

  
  

  I should ensure that the comparison options of the `Invoke-DatabaseBuild` function matches my Flyway Desktop json comparison options.

  
  

  Thanks!
  

  fwin September 15, 2022 04:19

  - 0 +

Add comment

Please sign in to leave a comment.