--
You received this message because you are subscribed to the Google Groups "jOOQ User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jooq-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/462ba013-0359-4e89-94ae-d5dddf0c8038%40googlegroups.com.
Hi Adam,The best approach is to write your own data type binding for the various range types and attach that to your schema in your code generator configuration:Whether you use a jOOλ type in your client code, or a Guava type, or something else is up to your own preferences.I hope this helps,Lukas
On Thu, Mar 5, 2020 at 5:48 AM Adam Zell <zell...@gmail.com> wrote:
Hello,--I am using Postgres 11 and have a number of tables that need range boundaries. The ranges could be implemented using two separate columns, or one column using https://www.postgresql.org/docs/11/rangetypes.html .Reading through the following links, I am not sure what the current best practice is for using int4range, etc:https://stackoverflow.com/questions/44959037/update-a-postgres-daterange-with-jooq/44964836#44964836What approach (assuming jOOQ 3.13.1) is recommended?Thanks!
You received this message because you are subscribed to the Google Groups "jOOQ User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jooq...@googlegroups.com.