What's the chance if you're not upgrading at all?

Optional<Boolean> is a 4 valued boolean. Would be 5 valued in JavaScript, even.

I obviously mean to use this mostly for emails to customer purchasing departments.

I forgot Redshift. You can check out the full list here, as well as emulations:

www.jooq.org/doc/latest/m...

I just had to check if it's that, or Factorio signal wires.

The green and red lines are from an airplane?

I mostly work with Eclipse and my "real world examples" aren't so real world, so it would take some time to make up a more meaningful example...

That would be awesome, and I know exactly what you mean :)

Unrelated to QUALIFY, but regarding Derby, it looks like it's going to be retired: issues.apache.org/jira/browse/...

I'm not convinced anyone else will continue developments

Also, if the type is used at the "top level" of a query, then it's easy to implement a data type binding for it in jOOQ, which takes care of reading from / writing to JDBC.

These edge cases appear mainly when deserialising UDTs containing such types, which is probably a rare feature combination.

jOOQ doesn't explicitly support the box type. So far, most people who used some sort of geometry type used this via PostGIS, which exposes its data as WKT or WKB.

I might add support for box et al. if someone asks for it.

Actually, when reading these arrays, jOOQ could still attempt to parse the syntax. jOOQ's already parsing most of PG's object notation (e.g. when ROW, UDTs, etc are serialised, as pgjdbc doesn't really help here), so why not support this as well.

1 user in 10 years might be very happy :)

I'll implement an UnsupportedOperationException

OK found it. ARRAY_LOWER can help, I guess:
dbfiddle.uk/pxomTqPm