Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Action composition is not sufficient to do the job, but Action composition + Future, or Action composition + Actors are good ways to achieve this.</p> <p><strong>Action Composition + Future</strong></p> <p>Generate your Response, launch your logging/processing in an <strong>async</strong> context and, in parallel, send the result.</p> <pre class="lang-scala prettyprint-override"><code>def LoggedAction(f: Request[AnyContent] =&gt; Result) = Action { request =&gt; val result = f(request) concurrent.future(myLogAction(request, result)) result } </code></pre> <p><strong>Action composition + Actors</strong></p> <p>It's a cleaner way to achieve that. As in the previous case, generate your response, send logging/processing event to your(s) actor(s), and in parallel, send the result.</p> <pre class="lang-scala prettyprint-override"><code>import play.api._ import play.api.mvc._ import play.libs._ import akka.actor._ object Application extends Controller with Finally { def index = LoggedAction { r =&gt; Ok(views.html.index("Your new application is ready.")) } } trait Finally { self: Controller =&gt; lazy val logActor = Akka.system.actorOf(Props(new LogActor), name = "logActor") def LoggedAction(f: Request[AnyContent] =&gt; Result) = Action { request =&gt; val result = f(request) // Generate response logActor ! LogRequest(request) // Send log event to LogActor println("-&gt; now send page to client") result } case class LogRequest(request: Request[AnyContent]) class LogActor extends Actor { def receive = { case LogRequest(req) =&gt; { println(req.host) // .... } } } } // Console -&gt; now send page to client 127.0.0.1:9000 </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PO@Finally equivalent in play 2.0.x?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJulien Lafont
    1. USJulien Lafont
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO@Finally equivalent in play 2.0.x?
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    1. COthis is what I was looking for, thanks!
      singulars
      1. PO
      1. USdhore
 

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