We should use MockConnector to simulate connector that support missing columns on insert and test if row filtering is properly handled if columns are missing during the insert but used in row filters.

Related to: #10006 and #10005

The .forall pattern is a great way to create an optional filter for a field that could be defined or not:

case class Person(name: String, age: Int)
val nameOpt: Option[String] = Some("Joe")
run { query[Person].filter(p => lift(nameOpt).forall(_ == p.name)) }
// SELECT p.name, p.age FROM Person p WHERE ? IS NULL OR ? = p.name
// (i.e. when nameOpt := None then the `WHERE ? IS NULL`

1 issue description
2. fix bug, enhance....
3. git commit -m "issue name (#issue number)"

Currently the CodeGenerator provides utility methods such as findBy/findAll.
It would be great to provide a method such as:

def foreach(where: SQLSyntax)(item: ${className} => Unit)(implicit session: DBSession$defaultAutoSession): Unit = {
  sql"select xxx where $${where}".foreach { record => item(record) }
}

I'm submitting a ...

• bug report
• feature request

Context
The Changelog RRS feed can be found on the Changelog page:
https://jdbc.postgresql.org/documentation/changelog.html
Just above the section "Introduction and explanation of symbols". Direct link:
https://jdbc.postgresql.org/change

Describe the proposal

When a SparkConf is invalid for launching our engines, it is better to fail fast instead of waiting for Spark to check while engine bootstrapping.

Motivation

1. Save time to create an invalid