[Play-2.5 +] ApplicationEvolutions.runEvolutions should be protected rather than private

[Rajendra Prasad Gujja]

The evolutions and DBApi are so constrained with multi-tenant applications where "Database" and "EvolutionConfig" is dynamic. We use schema-per-tenant model, every tenant will have its own database and tenant can be created dynamically (from a Super Admin UI). 

At the start of the server, we would like to get all the tenants and apply evolutions onto all the tenants. Another complexity we have is, there is one single common database along with multiple tenant databases and there could be evolutions to that "common" db as well.

What we are doing currently is, we took an easy approach using "Evolutions.applyEvolutions" by providing custom "EvolutionsReader", but the limitation with this approach is we are missing all the configurable properties like "lock evolutions table" and "Don't apply Downs" etc. 

We are trying to override "ApplicationEvolutions" and pass our own "Database" to "runEvolutions", unfortunately it is not "overridable".

Anyone disagree with me or any other approach you suggest?

Thanks!

[Will Sargent]

Evolutions has multiple issues, and doesn't deal well with complex situations like repeatable or conditional schema evolutions.  If you're planning on doing a schema per tenant and have multiple databases, I'd suggest using Flyways to do your evolutions in scope -- see this example:

https://github.com/playframework/play-scala-isolated-slick-example/blob/master/test/controller/MyApplicationFactory.scala

--

Will Sargent

Engineer, Lightbend, Inc.

will.s...@lightbend.com

--
You received this message because you are subscribed to the Google Groups "Play framework dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framework-dev+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.