| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| Cc: | Oliver Jowett <oliver(at)opencloud(dot)com>, Barry Lind <blind(at)xythos(dot)com>, pgsql-jdbc(at)postgresql(dot)org, g(dot)tomassoni(at)libero(dot)it |
| Subject: | Re: Comments on adding more connection URL parameters. |
| Date: | 2004-02-04 07:13:24 |
| Message-ID: | 7358.1075878804@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Kris Jurka <books(at)ejurka(dot)com> writes:
> Yes, supporting all GUC options is something we certainly wouldn't want to
> do by providing a method for each one. Especially since different server
> versions have different options and syntax. I imagine setGUC(String name,
> String value) would be sufficient. I suppose also we would have to be
> aware of GUC options that the driver sets itself (like datestyle and
> client_encoding) to ensure that these are not overwritten.
One minor gripe here: GUC is a server-implementation acronym that really
shouldn't be exposed as part of a client API, because it means nothing
to the average user. Can we do something that refers to "server
parameters" instead?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Juriy Goloveshkin | 2004-02-04 08:34:48 | Re: metadata searching |
| Previous Message | Kris Jurka | 2004-02-04 06:50:36 | Re: Comments on adding more connection URL parameters. |