Why I need to specify a query detection pattern?

JDBC manages 2 kinds of statement: query statement that fetches rows, or updates statement that update persistent data.

To supports this behaviour, to return rows when you consider statement to be a query, or update state/count when it should be an update, Acolyte should be taught how to detect these cases.

Using composite handler, you can specify it using detection pattern(s) (regular expressions):

import java.util.regex.Pattern
import acolyte.jdbc.CompositeHandler;

CompositeHandler handler1 = CompositeHandler.empty().
  // Considers as query if starts with 'SELECT ' or contains 'EXEC fetch_data'
  withQueryDetection("^SELECT ", "EXEC fetch_data"). 
  // Variant with pre-compiled pattern
  withQueryDetection(Pattern.compile("ORDER BY test$"));

In previous example, the handler is given different patterns. In such case, order in which patterns were given is used to check executed statement, until it matches at least one of them.

Equivalent with the Scala DSL is:

import java.util.regex.Pattern
import acolyte.jdbc.AcolyteDSL.handleStatement

val handler2 = handleStatement.
  withQueryDetection("^SELECT ", "EXEC fetch_data"). 
  withQueryDetection(Array(Pattern.compile("ORDER BY test$")))

With Scala DSL, if you want all statements to be considered as queries, you can use:

import acolyte.jdbc.QueryExecution
import acolyte.jdbc.AcolyteDSL.handleQuery

val handler3 = handleQuery { e: QueryExecution =>
  // handleQueries
  ??? // query results
}

What is the maximum number of column for a row?

Implementations of Row and RowList are provided up to 52 columns.

How to simply return a single scalar row?

If you just need to mock up a result containing only 1 row with 1 column, single column factories (booleanList, byteList, intList, stringList, …) can be called, or in Scala single value can be directly used (e.g. 2 for a single row with only one integer column).

Why do I get an error like “overloaded method value rowListX with alternatives” from Scala compiler?

Example: overloaded method value rowList6 with alternatives: [error] [A, B, C, D, E, F](x$1: acolyte.jdbc.RowList.Column[A], x$2: acolyte.jdbc.RowList.Column[B], x$3: acolyte.jdbc.RowList.Column[C], x$4: acolyte.jdbc.RowList.Column[D], x$5: acolyte.jdbc.RowList.Column[E], x$6: acolyte.jdbc.RowList.Column[F])acolyte.jdbc.RowList6[A,B,C,D,E,F] <and> [error] [A, B, C, D, E, F](x$1: Class[A], x$2: Class[B], x$3: Class[C], x$4: Class[D], x$5: Class[E], x$6: Class[F])acolyte.jdbc.RowList6[A,B,C,D,E,F] [error] cannot be applied to ((Class[String], String), (Class[String], String), (Class[String], String), (Class[String], String), (Class[String], String), (Class[String], String))

It occurs when acolyte.jdbc.Implicits.PairAsColumn is missing while using the pimped Scala syntax to declare row list:

import acolyte.jdbc.Implicits._
import acolyte.jdbc.RowLists.rowList6

// Corresponding to error example
// - will raise compilation error
rowList6(
  classOf[String] -> "col1", 
  classOf[String] -> "col2",
  classOf[String] -> "col3",
  classOf[String] -> "col4",
  classOf[String] -> "col5",
  classOf[String] -> "col6")

Adding the proper import fixes that.

import acolyte.jdbc.RowLists.rowList6
import acolyte.jdbc.Implicits.PairAsColumn // or acolyte.jdbc.Implicits._

rowList6( // Now it's ok
  classOf[String] -> "col1", 
  classOf[String] -> "col2",
  classOf[String] -> "col3",
  classOf[String] -> "col4",
  classOf[String] -> "col5",
  classOf[String] -> "col6")

Can I re-use data from existing DB with Acolyte?

Studio can record results from DB, so they can be used later with Acolyte framework, either in Java or Scala.

Why do I get error with null value in row?

As type can’t always be inferred when using null, it can lead to ambiguity:

[error]  found   : Null(null)
[error]  required: Int

In such cases, type of null must be explicitly given (cast).

Why do I get type arguments error in Scala 2.11?

If you use Acolyte with Scala 2.11, and have in your code reference to row list types like RowList4[String, String, String, String, _], you may get a compilation error as following one:

...: type arguments [String,String,String,String,_$1] do not conform to class RowList4's type parameter bounds [A,B,C,D,UPDATED <: acolyte.jdbc.RowList4[A, B, C, D, _]] ...

This seems to be due to change in Scala compiler about self-types. Fortunately that’s not a big deal to fix it, by changing type reference like RowList4[A, B, C, D, _] to something like RowList[Row4[A, B, C, D]] (concrete type where self-type is resolved).