jdbc

Instead of creating on the fly an Iceberg table with Trino and run queries against it, use static resources for setting up an Iceberg test environment which can be used to read Iceberg v1 / v2 tables and guard trino-iceberg plugin against regresssions.

Related discussion: trinodb/trino#11642 (comment)

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)"

the postgres:

version - PostgreSQL 13.4 (Debian 13.4-4.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit

the DDL:

create table test (
  id bigint,
  name text
)

the build.sbt:

name := "scalikejdbc-hikari-postgres-connection-leaks"
scalaVersion := "2.12.15"

libraryDependencies ++= Seq(
  "org.postgresql" % "

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

Code of Conduct

• I agree to follow this project's Code of Conduct

Search before asking

• I have searched in the issues and found no similar issues.

What would you like to be improved?

code refraction

How should we improve?

No response

Are