Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is a tentative answer as I have currently tested on play 2.2.0 and I can't reproduce your bug, using a MYSQL database. </p> <p>I feel there might be a very tricky bug in your code. First of all, if you explore the DBPlugin implementation provided by Play, BoneCPPPlugin:</p> <pre><code> /** * Closes all data sources. */ override def onStop() { dbApi.datasources.foreach { case (ds, _) =&gt; try { dbApi.shutdownPool(ds) } catch { case NonFatal(_) =&gt; } } val drivers = DriverManager.getDrivers() while (drivers.hasMoreElements) { val driver = drivers.nextElement DriverManager.deregisterDriver(driver) } } </code></pre> <p>You see that the onStop() method closes the connection pool. So it's clear, you are providing to the second test example an application which has already been stopped (and therefore its plugins are stopped and the db connectin pool closed).</p> <p>Scalatests and specs2 run the test in parallel, and you can rely on the test helper because it's thread-safe:</p> <pre><code> def running[T](fakeApp: FakeApplication)(block: =&gt; T): T = { synchronized { try { Play.start(fakeApp) block } finally { Play.stop() play.api.libs.ws.WS.resetClient() } } } </code></pre> <p>However, when you do </p> <pre><code>DB.getDataSource("test") </code></pre> <p>From the source code of Play: </p> <pre><code> def getDataSource(name: String = "default")(implicit app: Application): DataSource = app.plugin[DBPlugin].map(_.api.getDataSource(name)).getOrElse(error) </code></pre> <p>So here there is an implicit, does which not get resolved to FakeApplication (it is not an implicit in scope!!!), but to <code>Play.current</code> and it appears that in the second case, this is not what you were expecting it to be, Play.current still point to the previous instance of FakeApplication: it probably depends on how implicit are captured in closures</p> <p>If you however, refactor the fakeApp method, you can ensure the application you just created is used to resolve the implicit (you can always make explicit the value for an implicit parameter)</p> <pre><code> def fakeApp[T](block: =&gt; T): T = { val fakeApplication = FakeApplication(additionalConfiguration = postgresDatabase("test") ++ Map("evolutionplugin" -&gt; "disabled")) running(fakeApplication) { def database = Database.forDataSource(DB.getDataSource("test")(fakeApplication)) database.withSession { implicit s: Session =&gt; block } } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POPlay 2.1 Unit Test With Slick and Postgres
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USEdmondo1984
    1. USEdmondo1984
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COEdmondo, excellent sleuthing! This does move things forward. I now get "RuntimeException: There is no started application" when running from the command line, unfortunately. I made a gist with all the relevant files https://gist.github.com/mslinn/8046542
      singulars
      1. PO
      1. USMike Slinn
    2. COcan you provide an sbt project on a github repo? I am missing application.conf which is imported in test.conf and would be tooh ard to debug. In your gist I see you still have play.api.Play.current as an import. I would remove it to see what happens
      singulars
      1. PO
      1. USEdmondo1984
    3. COTry again with the change I made here - https://gist.github.com/drstevens/8048116/f181c671c64df210e37197a30a5801e25f6014fc
      singulars
      1. PO
      1. USdrstevens
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload