Hi Max, That's very interesting, thanks for linking. I wasn't aware of this PostgreSQL specific behaviour. That's weird. The main reason for using collations is to override sort behaviour as far as I have learned this from other databases. I suspect there is some historic reason why this isn't currently the case in PostgreSQL.
CITEXT is a useful data type, but sometimes, you want to have case sensitive content but only sort (or filter) things case insensitively on an ad-hoc basis. In any case, https://github.com/jOOQ/jOOQ/issues/7882 is implemented for jOOQ 3.12. For the time being, you can work around the missing feature by using LOWER() yourself in your own code. Thanks again for the pointers, Lukas On Fri, Sep 21, 2018 at 5:38 PM Max Kremer <mkre...@trialfire.com> wrote: > Sorry one more : https://postgrespro.com/docs/postgresql/10/collation > > Relevant text : ''Note that while this system allows creating collations > that “ignore case” or “ignore accents” or similar (using the ks key), > PostgreSQL does not at the moment allow such collations to act in a truly > case- or accent-insensitive manner. Any strings that compare equal > according to the collation but are not byte-wise equal will be sorted > according to their byte values." > > -- > 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+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
