Re: BUG #16028: JDBC currentSchema connection parameter not working for text search configuration

Interesting,

Thanks for the report.

Dave Cramer

On Thu, 26 Sep 2019 at 18:16, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:

> The following bug has been logged on the website:
>
> Bug reference: 16028
> Logged by: cd a
> Email address: cdalxndr(at)yahoo(dot)com
> PostgreSQL version: 10.3
> Operating system: Windows 10
> Description:
>
> Using a java spring app with connection:
>
> jdbc:postgresql://localhost:5433/postgres?currentSchema=dev,public&ApplicationName=myapp
> Schema 'dev' has fts configuration 'en'.
> Query (debugged PgPreparedStatement):
> select * from dev.category where category.language='en'
> the param 'en' is registered with oid (paramType) 3734 corresponding to
> 'regconfig' type
>
> Query results in: ERROR: text search configuration "en" does not exist
>
> The same error is shown when running the query in PgAdmin if search_path
> doesn't contain 'dev' schema. With 'dev' in search_path, the query is ok.
> I was expecting that 'currentSchema' connection parameter will be used to
> resolve fts configuration to 'dev' schema.
>
>