Evolutions is enabled by default on all existing database connections.
Reported by Zenklys | July 12th, 2012 @ 09:38 AM
When using multiple database connections in a PlayFramework project and using evolutions, the framework assumes evolutions is used on all databases and thus creates the play_evolutions table on each database.
Expected behaviour :
A Play project can have it's own database managed with evolutions and need to connect to an existing database without managing the external database with evolutions.
Simple example :
A concrete example would be SSO (in a very basic way). The Play app has it's own database and data but delegates user management to a 3rd party application.
Comments and changes to this ticket
Ok, sorry, my fault, the issue was already reported.
If someone could close the issue.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »