How can we help you today? How can we help you today?
Peter_Laws
Hi JonBrune, Thanks for thinking of us, I'll add the obligatory documentation at the end, but first I'll talk you through it because docs can be a little dry. Firstly version numbers have to be unique and the description isn't factored in, it's just the value preceding the double underscore. If you attempt it, you'll see this kind of exception: C:\Users\Peter.Laws\Desktop\Flyway\flyway-commandline-9.18.0-windows-x64\flyway-9.18.0>flyway info Licensed to red-gate.com Database: jdbc:postgresql:postgres (PostgreSQL 14.2) ERROR: Found more than one migration with version 1 Offenders: -> C:\Users\Peter.Laws\Desktop\Flyway\flyway-commandline-9.18.0-windows-x64\flyway-9.18.0\sql\V1__first - Copy (2).sql (SQL) -> C:\Users\Peter.Laws\Desktop\Flyway\flyway-commandline-9.18.0-windows-x64\flyway-9.18.0\sql\V1__first - Copy.sql (SQL)By extension, this approach makes the ordering much more intuitive, alphanumeric ordering is typically slower to groc at a glance. For the other points Flyway validate has your back here and will handle each of these scenarios, better yet, you don't actually have to do anything because it's always checked prior to performing a migration. Looking at the schema history table that records the migrations, you'll see a checksum is taken at runtime/ [image] [image] So should a migration be altered (ill intentioned or otherwise) when the scrips are parsed at time of migration, flyway will itnerupt itself and inform you if any script checksums have changed, even if they wouldn't been run (due to having already been deployed) to make sure they aren't unintentionally implemented against another target introducing unknown variables. Regarding order, if a new, earlier version is introduced, flyway will warn you that there are now new, out of order migrations that could be applied, so you can choose how to proceed. Nearly everything I've listed here can be configured, this is just the default behaviour. Thanks for contributing to the forum! Documentation Migrations naming conventions Validate OutOfOrder and CherryPick / comments
Hi JonBrune,Thanks for thinking of us, I'll add the obligatory documentation at the end, but first I'll talk you through it because docs can be a little dry.Firstly version numbers have to be uniqu...
0 votes
My apologies for the rather weak reply tpurcell, are you able to confirm please that the version of flyway running matches your dependencies and isn't running something older unintentionally? I ask because coping your code & maven dependencies returns: ################# START PLUGIN CLASSES PLUGIN CLASS: CockroachDBDatabaseType, VERSION: null PLUGIN CLASS: RedshiftDatabaseType, VERSION: null PLUGIN CLASS: DB2DatabaseType, VERSION: null PLUGIN CLASS: DerbyDatabaseType, VERSION: null PLUGIN CLASS: H2DatabaseType, VERSION: null PLUGIN CLASS: HSQLDBDatabaseType, VERSION: null PLUGIN CLASS: InformixDatabaseType, VERSION: null PLUGIN CLASS: OracleDatabaseType, VERSION: null PLUGIN CLASS: PostgreSQLDatabaseType, VERSION: null PLUGIN CLASS: SAPHANADatabaseType, VERSION: null PLUGIN CLASS: SnowflakeDatabaseType, VERSION: null PLUGIN CLASS: SQLiteDatabaseType, VERSION: null PLUGIN CLASS: SybaseASEJConnectDatabaseType, VERSION: null PLUGIN CLASS: SybaseASEJTDSDatabaseType, VERSION: null PLUGIN CLASS: TestContainersDatabaseType, VERSION: null PLUGIN CLASS: BaseAppliedMigration, VERSION: null PLUGIN CLASS: CoreResourceTypeProvider, VERSION: null PLUGIN CLASS: PostgreSQLConfigurationExtension, VERSION: null PLUGIN CLASS: CleanModeConfigurationExtension, VERSION: null PLUGIN CLASS: EnvironmentVariableResolver, VERSION: null PLUGIN CLASS: SpannerDatabaseType, VERSION: null PLUGIN CLASS: SpannerDatabaseExtension, VERSION: null ################# END PLUGIN CLASSESSSES / comments
My apologies for the rather weak reply tpurcell, are you able to confirm please that the version of flyway running matches your dependencies and isn't running something older unintentionally?I ask ...
0 votes
Hello JR_AUS, thanks for the question. Probably not in the near future, as you can see here, the prefered and encouraged dev configuration is dedicated so it's less of a priority than in the SQL Source Control context. / comments
Hello JR_AUS, thanks for the question.Probably not in the near future, as you can see here, the prefered and encouraged dev configuration is dedicated so it's less of a priority than in the SQL Sou...
0 votes