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

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: cdalxndr(at)yahoo(dot)com
Subject: BUG #16028: JDBC currentSchema connection parameter not working for text search configuration
Date: 2019-09-26 22:15:13
Message-ID: 16028-3b4724da97a51b77@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2019-09-27 01:36:15 Re: BUG #16026: default_tablespace in postgresql.conf is used instead of the database's default.
Previous Message Daniel Verite 2019-09-26 16:39:40 Re: BUG #16020: ICU Collations querys