Matthias Kurz
Matthias Kurz
> I also tried "-Debean.ddl.generateProcedures=false" in javacOptions. This will not work. First its not a compiler option. Second you need to set it on the jvm instance that is running...
Also [since 8.1.0](https://github.com/playframework/play-ebean/releases/tag/8.1.0) you can disable the generation of the evolutions scripts (in app conf): ``` play.ebean.generateEvolutionsScripts = false ```
You say you have an existing application that you migrate, so i think you already have evolution files? Just 1 or more? Or what, with Play 2.8 is your current...
> we used to get new evolution files generated How? Like if you already have lets say 7 evolution files, was the 8th generated automatically? How? Who did generate that...
OK I get it. I try to figure something out.
Opened - https://github.com/playframework/playframework/issues/12968 Let's see if we can convince the ebean author [to help out here a bit](https://github.com/ebean-orm/ebean/pull/3408#issuecomment-2473492569).
> btw, if I add `-Debean.ddl.generateProcedures=false` to .jvmopts file. I get the error "_ddl has type OBJECT rather than LIST_" Please open a separate issue in this repo for that....
I think the simplest solution is to parse the sql script returned by ebean and convert it to play evolutions compatible sql. It's not the nicest solution, but it will...
not stale
Not stale