Adil Aijaz

And I think I don't even require procedures. and there seems to be no way to turn off generating procedures

I can’t turn off generating the evolution scripts, because I can’t write SQLs for like 20 schemas. I want play-ebean to generate and execute them for me.

Is there any proper solution of this bug apart from turning off generating procedures (which is unclear what exactly to do as I don’t have much knowledge about jvm options)

On development, we used to get new evolution files generated and applied automatically whenever there's a change in one or more entities. This was because we have: ``` play.evolutions {...

play-ebean generates/replaces the evolution files in "/evolutions/default/1.sql" "/evolutions/local/1.sql" so it's always one SQL file that's regenerated by play-ebean. We are not used to even touching those SQL files.

btw, if I add `-Debean.ddl.generateProcedures=false` to .jvmopts file. I get the error "_ddl has type OBJECT rather than LIST_"