Play Version

Play 2.5.12

API

Java

Operating System (CentOS 7)

Linux terra.localdomain 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

JDK (Oracle JDK)

java version "1.8.0_102"
Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)

Expected Behavior

Allowing usage of extended filename for Evolution SQL scripts.

By example :

1.sql // Automatically generated by sbt-play-ebean module
2__alter-account.sql
3_0__create-table.sql
3_1__new-indexes.sql
4.sql

Actual Behavior

Can only create basic name like 1.sql, 2.sql, 3.sql, 4.sql, ...

Proposal

Why not just scanning evolution directory and run founded files (ordered by filename) rather than try to open a fixed file pattern and stop evolution when n.sql does not exists ?

It could be nice to use a different pattern for "dev" and "production" too. Why ? cause when we run Play in "dev" mode, it could be useful to seed created DB with test data or force Evolution to recreate 1.sql each time a Model is modified.