Re: citext plugin is not working with java applications

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: berthuijgen(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: citext plugin is not working with java applications
Date: 2019-01-22 06:00:41
Message-ID: CAKFQuwaDCHHveSXeo6xNgQWgGp4ExinDZAdXjng1zHxdFAEtPQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Mon, Jan 21, 2019 at 7:39 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> You have not explained what "does not work" means.

True...but assuming it is true would we accept placing a
driver-specific warning here? We do not do so anywhere else in the
documentation that I am aware.

The main issue, IIUC, is that Prepared Statements require their input
types to be known while most users write queries without specifying
data types explicitly. The JDBC driver falls back to determining the
untyped input as text instead of citext which forces a "text op text"
comparison instead of a "citext op citext" one when the query is
executed.

The JDBC docs don't seem to cover this, which they should as it is
their limitation, not ours (that I am aware of...), though I'm unsure
exactly what the limitation stems from.

David J.

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Pavlo Golub 2019-01-22 12:26:40 `transaction_read_only` GUC undocumented
Previous Message Bruce Momjian 2019-01-22 02:39:15 Re: citext plugin is not working with java applications