| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5304: psql using conninfo fails in connecting to the server |
| Date: | 2010-02-03 01:50:46 |
| Message-ID: | 4B68D676.4000208@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 02/02/2010 05:46 PM, Fujii Masao wrote:
> On Wed, Feb 3, 2010 at 10:05 AM, Joe Conway <mail(at)joeconway(dot)com> wrote:
>> Objections?
>
> I think that PQconnectdbParams() rather than psql should handle the
> dbname containing "=". Otherwise whenever we use PQconnectdbParams(),
> we would have to check for the content of the dbname before calling
> it in the future application. Which looks very messy for me.
But I thought the whole point of PQconnectdbParams() was to provide an
extensible way to accept parameters when they are already parsed? It
doesn't make any sense to me to have conninfo parsing capability built
into PQconnectdbParams(). For that matter it's kind of an ugly hack that
PQsetdbLogin() supports it, IMHO.
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-02-03 01:59:20 | Re: BUG #5304: psql using conninfo fails in connecting to the server |
| Previous Message | Fujii Masao | 2010-02-03 01:46:14 | Re: BUG #5304: psql using conninfo fails in connecting to the server |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-02-03 01:59:20 | Re: BUG #5304: psql using conninfo fails in connecting to the server |
| Previous Message | Fujii Masao | 2010-02-03 01:46:14 | Re: BUG #5304: psql using conninfo fails in connecting to the server |