Databases
StackOverflow2013
Postsdbo
POHow to set up PostgreSQL for Play 2.0?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to set up PostgreSQL for Play 2.0?
    primarykey
    data
    text
    <p>I'd like to configure PostgreSQL for my Play app, but am getting the following error:</p> <pre><code>! Internal server error, for request [GET /] -&gt; java.util.concurrent.TimeoutException: Futures timed out after [300000] milliseconds at akka.dispatch.DefaultPromise.ready(Future.scala:834) ~[akka-actor.jar:2.0] at akka.dispatch.DefaultPromise.result(Future.scala:838) ~[akka-actor.jar:2.0] at akka.dispatch.Await$.result(Future.scala:74) ~[akka-actor.jar:2.0] at play.core.ReloadableApplication.get(ApplicationProvider.scala:108) ~[play_2.9.1.jar:2.0] at play.core.server.Server$class.sendHandler$1(Server.scala:59) [play_2.9.1.jar:2.0] at play.core.server.Server$$anonfun$getHandlerFor$4.apply(Server.scala:89) [play_2.9.1.jar:2.0] [error] application - ! @6a64i2p5o - Internal server error, for request [GET /] -&gt; play.api.PlayException: Not initialized [?] at play.api.PlayException$.apply(Exceptions.scala:122) ~[play_2.9.1.jar:2.0] at play.core.ReloadableApplication.&lt;init&gt;(ApplicationProvider.scala:94) ~[play_2.9.1.jar:2.0] at play.core.server.NettyServer$$anonfun$mainDev$1.apply(NettyServer.scala:165) ~[play_2.9.1.jar:2.0] at play.core.server.NettyServer$$anonfun$mainDev$1.apply(NettyServer.scala:164) ~[play_2.9.1.jar:2.0] at play.utils.Threads$.withContextClassLoader(Threads.scala:17) ~[play_2.9.1.jar:2.0] at play.core.server.NettyServer$.mainDev(NettyServer.scala:163) ~[play_2.9.1.jar:2.0] </code></pre> <p>I use the following configuration files:</p> <p><strong>application.conf</strong></p> <pre><code>db.default.url="postgres://play:play@localhost:9000/Play_Playground_DB" db.default.user=play db.default.password=play db.default.driver=org.postgresql.Driver </code></pre> <p><strong>project/Build.scala</strong></p> <pre><code>val appDependencies = Seq( "postgresql" % "postgresql" % "9.1-901.jdbc4" ) </code></pre> <p>I set up <code>Play_Playground_DB</code> and can access it via terminal and the command <code>psql Play_Playground_DB</code>.</p> <p>What could be the root cause of the issue?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJacek Laskowski
    1. USThomas Kremmel
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to set up PostgreSQL for Play 2.0?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to set up PostgreSQL for Play 2.0?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow to set up PostgreSQL for Play 2.0?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThat URL is not anything PostgreSQL would recognize; presumably the framework is taking that apart and picking out the pieces needed? Also, I recommend that you read this section and update your driver jar: http://jdbc.postgresql.org/download.html#current
      singulars
      1. POHow to set up PostgreSQL for Play 2.0?
      1. USkgrittn
    2. COThanks! Updated it to the current version.
      singulars
      1. POHow to set up PostgreSQL for Play 2.0?
      1. USThomas Kremmel
 

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