anorm

Up until the anorm included with play 2.3, I could write the following: implicit val arbitraryClassToStatement = new ToStatement[ArbitraryClass] { def set( s: java.sql.PreparedStatement, index: Int, aValue: ArbitraryClass ) : Unit = { s.setString( index, ArbitraryClass.definingString ) } } and this would help insert the SQL("INSERT INTO SomeTable Values( {nonNullAc}, {possiblyNullAc} )" ).on( 'nonNullAc -> ArbitraryClass( "abcd" ), 'possiblyNullAc -> Option( ArbitraryClass( "abcd" ) ) ) meaning that both ArbitraryClass and Option[ ArbitraryClass ] would be satisfied by it. This seems to no

Given rowParser of type RowParser[Photo] , this is how you would parse a list of rows coming from a table photo , according to the code samples I have seen so far: def getPhotos(album: Album): List[Photo] = DB.withConnection { implicit c => SQL("select * from photo where album = {album}").on( 'album -> album.id ).as(rowParser *) } Where the * operator creates a parser of type ResultSetParser[List[Photo]] . Now, I was wondering if it was equally possible to get a parser that yields a Stream (thinking that being more lazy is always better), but I only came up with this: def getPhotos(album:

I just started working with play, and I modified the way I'm doing a SQL read and I'm now getting the following error: [Exception: DB plugin is not registered.] The code I have for this class is: package models import play.api.db._ import play.api.Play.current import anorm._ case class Housing(id: Long, rent: String, address: String, street0: String, street1: String, neighbourhood: String) object Housing { def all(): List[Housing] = DB.withConnection { implicit c => SQL("select * from housing")().map { row => Housing(row[Long]("id"), row[String]("rent"), row[String]("address"), row[String](

With Play 2.4.0 Anorm got moved to an external package and logging got changed to LogBack ( http://logback.qos.ch ) All well and good but nowhere are the class/package names obvious for tracing SQL calls. The "obvious" (based on the import statements) <logger name="anorm" level="TRACE" /> did nothing and I also tried <logger name="anorm.SQL" level="TRACE" /> just in case it needed to be more specific. Google searches just dead needed so I'm at a loss. Anyone? You can intercept calls going thru JDBC driver using log4jdbc I have used successfully with JPA/hibernate and Hikary on Play 2.4, the

What is the current sbt syntax for using a recent version (say, 2.3 or 2.4) of Play's anorm package in standalone mode (not part of a Play application)? Anorm is now published as follows with no need for an additional resolver. "org.playframework.anorm" %% "anorm" % "2.6.2" In build.sbt : resolvers ++= Seq( "Typesafe Releases" at "http://repo.typesafe.com/typesafe/releases/") libraryDependencies ++= Seq( "com.typesafe.play" %% "anorm" % "2.3.6") See example . 来源： https://stackoverflow.com/questions/25532080/how-to-declare-dependency-on-plays-anorm-for-a-standalone-application

I'm studying a little the anorm documentation (from play framework) and is not clear if it supports a common query use case: dynamic filters, that is the user fills in 2 or 3 search criteria on a 10 fields search form. In this case how can I dynamically construct the query without the classic string manipulation? Yes, I think the question referenced by Robin Green contains the answer. Just define your query with all the possible criteria using placeholders (e.g. {criterion1} ) and call the on() method on the query, passing the actual Seq of Option parameters as described in the accepted answer