Comments
Sort by recent activity
Thank you both! / comments
Thank you both!
Thanks for the reply Christian, however I have since blown away the project for which I was getting this error, and a have cloned a new project from our Git repository. The project in question was created from scratch, with DDL files being copied into the schema-model after project creation. The error was encountered in Flyway Desktop while trying to refresh the comparison between schema model and dev database. When I get time, I will try to recreate and provide the resulting .toml file. / comments
Thanks for the reply Christian, however I have since blown away the project for which I was getting this error, and a have cloned a new project from our Git repository. The project in question was...
Thanks for the reply, Jon. I tried adding the sqlMigrationSuffixes setting to our .toml file (Flyway Desktop), however the objects for which the DDL files have different extensions still were not picked up in the schema model. I will have to revert to prefixing the file names with the object types. Some database tools (e.g. Toad for Oracle) save the files with different extensions to indicate the type of object being created. Even though the files are stored in separate folders in our repository, it's our preference to also have distinguishing naming conventions, and I was hoping to keep these extensions. / comments
Thanks for the reply, Jon. I tried adding the sqlMigrationSuffixes setting to our .toml file (Flyway Desktop), however the objects for which the DDL files have different extensions still were not ...