What is the difference between inSet and inSetBind in Slick

scala slick
Mike picture Mike · Oct 27, 2014 · Viewed 8.5k times · Source

The ScalaDoc of the functions has not been filled out.

I know that the methods are used for mimicking SQL's IN keyword (eg, SELECT * FROM table WHERE id IN VALUES(1, 42, 101) could be done with table.filter(_.id inSet Seq(1, 42, 101))). I don't know what this "bind" version is or how to choose which I should be using.

Answer

virtualeyes picture virtualeyes · Oct 27, 2014

inSet is an unsafe version of inSetBind which generates a safe/escaped sql value based on passed in input. In your example where the value is manually set, the two types of bind are equally safe.

Normally with bound parameters you get a performance boost (via generated prepared statement), but not the case with collection values. See here for the details.

Related questions

Slick 3.0 Insert and then get Auto Increment Value

I have written this code which works perfectly class Items(tag: Tag) extends Table[Item](tag, "ITEMS") { def id = column[Long]("ITEMS_ID", O.PrimaryKey, O.AutoInc) def name = column[String]("ITEMS_NAME") def price = column[Double]("ITEMS_PRICE") def * = (…

Read More
View SQL query in Slick

Is there a way to observe an SQL statement that will be generated by Query? For example, I have this: val q = actions.filter(v => v.actionHash === hash && v.carriedAt > past) Can I view its underlying …

Read More
Logging options for Slick

I'm createing a Play 2.1 app, in which I have decided to use Slick for database interaction. However I can't find documentation about how to configure/enable logging for Slick. Anyone knows this?

Read More