bad versions generated when using prefix

[Incanus3]

Hi guys. We just started experimenting with ebean-migration and encountered a strange problem with generated migration versions. We have a migration generation script like this:

fun main(args: Array<String>) {
    System.setProperty("spring.profiles.active", "kb-dev")
    System.setProperty("spring.main.banner-mode", "off")
    System.setProperty("spring.main.web-application-type", "none")
    System.setProperty("logging.level.root", "WARN")
    System.setProperty("kb.background.run-jobs", "false")
    System.setProperty("kb.architecture.load-registry-network", "false")

    val context = runApplication<QwazarKB>(*args)
    val database = context.getBean(INDEX_DB_QUALIFIER, Database::class.java)

    val migration = DbMigration.create().apply {
        setServer(database)

        addPlatform(Platform.H2)
        addPlatform(Platform.POSTGRES)
        addPlatform(Platform.ORACLE)
        addPlatform(Platform.SQLSERVER17)

        setIncludeIndex(true)

        setApplyPrefix("3.14.0-") // TODO: change before running!
        setName("add ZkratkaListRow") // TODO: change before running!

        // TODO: can we somehow deduce this?
        setPathToResources("backends/kb/src/main/resources")
    }

    migration.generateMigration()
}

Now, the first version looked as expected: 3.14.0-1.0, but after that, they started getting strange:

• second version: 3.14.0-3.14.0.1.1
• third version: 3.14.0-3.14.0.3.14.0.1.2

[rPraml]

We use 'V' as prefix. If you want to re-number your migrations, I think, you can just rename them. Ebean-migration should then derive the next version number from the filename. This is also, what seems to happen here: When you generate the second migration, it will try to derive the version from the previous file.
What's your exact use case, that you want to gsin, by putting a version number as prefix?

[Incanus3]

hi and thanks for the reply. the desired result here was that migration versions would be prefixed by the application version, so I would get 3.14.0-1.0, then 3.14.0-1.1, etc. Then if I increased the application version, I would get 3.15.0-1.0, 3.15.0-1.1, etc. I understand this might not be the intended usage of the prefix and I understand if it will not work, but it's really surprising how it keeps duplicating prefix with every new version.

[rbygrave]

I think the issue is with the "determination of the NEXT migration version" ... which is for migration generation and not this project per se [you won't find the code for that here in this project / this is for running migrations only].

Its likely you want to be looking at https://github.com/ebean-orm/ebean/blob/master/ebean-ddl-generator/src/main/java/io/ebeaninternal/dbmigration/LastMigration.java