title: Multiple database management with Playframework 2.0 and Ebean
body: <p>I'm on my first experience with Playframework, using 2.0. I'm having troubles configuring two databases to be managed with Eebean ORM (which is integrated into Play).
  Referring to this <a href="http://www.playframework.org/documentation/2.0/JavaEbean" rel="nofollow">documentation page</a>, I came up with:</p>
  
  <p>conf/application.conf</p>
  
  <pre><code>db.global.driver="com.mysql.jdbc.Driver"
  db.global.url="mysql://root:root@localhost/phdcoursedb"
  
  # In the developement environment this might even change backend
  db.statistics.driver="com.mysql.jdbc.Driver" 
  db.statistics.url="mysql://root:root@localhost/statistics"
  
  ebean.global="models.global.*"
  ebean.statistics="models.statistics.*"
  </code></pre>
  
  <p>And i wrote the correspondong models in models.globals and models.statistics packages.
  When I run the application, the evolution system asks me to upgrade (using the file generated by the Ebean DDL).
  The problem is, for BOTH databases it proposes me an evolution sql script which encapsulates ALL models (both in models.global and in models.statistics).</p>
  
  <p>Thing is, I'd like to keep Ebean DDL on for the second database (I don't actually need it for the other one, which is a legacy untouchable database), but I'd like it to build correct tables only.</p>
  
  <p>Can you see what I'm doing wrong?
  Actually I didn't deeply explored Ebean documentation, because it always refers to some configuration files which I don't know where to find, as Play! itself embeds Ebean.</p>
  
  <p>Thanks a lot</p>
  
  <p>Davide</p>