jdbc

The current test TestCassandraConnectorTest has some issues:

• Unrelated types in a table
  • It reduces maintainability when we want to add test cases to a type
• The definition and data are managed in the different class
  • We need to look for the different class when we want to check the expected values
• Less coverage in a type
  • Should test min, max, null
  • Should test DST, juli

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

When using UNION, with ORDER BY or LIMIT within a subexpression's SELECT statement, PostgreSQL requires the SELECT statement be enclosed in parentheses: https://stackoverflow.com/a/24024639 However, the following QueryDSL code causes a syntax error against Postgres because it doesn't generate those parentheses:

val i = Item.syntax("i")
selectFrom(Item.as(i)).orderBy(i.id).u

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.

Describe the bug

Maybe we shall use https://kyuubi.apache.org/docs/latest/index.html instead of a versio