pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: sehrope (@sehrope) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] PR #3606: fix: add support for multiple schemas via PgConnection.setSchema
Date: Wed, 07 Jan 2026 16:20:05 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
@davecramer I think we should leave this alone as there's no way to have a single string parameter handle both funky names _and_ lists of funky names without some kind of oddball / breaking behavior:
```sql
=> CREATE SCHEMA "bad,name";
CREATE SCHEMA
=> CREATE TABLE "bad,name"."postgres allows crazy things like this" (id int);
CREATE TABLE
=> \d "bad,name"."postgres allows crazy things like this"
Table "bad,name.postgres allows crazy things like this"
Column | Type | Collation | Nullable | Default
--------+---------+-----------+----------+---------
id | integer | | |
=> CREATE SCHEMA "even worse "" schema name with embedded double quote";
CREATE SCHEMA
```
The "split via commas with optional spaces" will not work. I think we should leave that stuff alone. Ditto for having the `getSchema()` method not change as it'd be breaking existing behavior too. Anybody that wants the full value can run `SHOW search_path`.
@cgm-aw If you want to set the search path to multiple values via JDBC properties, you can use `options` with a `-c foo,bar,baz` value to set multiple schemas in the search path. There's an example of that in the docs: https://jdbc.postgresql.org/documentation/use/#connection-parameters
view thread (19+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] PR #3606: fix: add support for multiple schemas via PgConnection.setSchema
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox