Re: [HACKERS] Decicision needed for connect statement - Mailing list pgsql-hackers

From Michael Meskes
Subject Re: [HACKERS] Decicision needed for connect statement
Date
Msg-id 199805071239.OAA30333@gauss.topsystem.de
Whole thread Raw
In response to Re: [HACKERS] Decicision needed for connect statement  ("Thomas G. Lockhart" <lockhart@alumni.caltech.edu>)
List pgsql-hackers
Thomas G. Lockhart writes:
> > Each missing entry will be set to the default value:
> > template1@localhost:5432.
>
> Looks good, though perhaps the default db should be the user's name?

Yes, of course. This example came just from me using the Debian release of
6.3 which opens template1 as default. I cannot run 6.4, so I have to test
with the old version.

I do not enter a default myself, but rather let PQsetdb handle it.

> Is there any benefit to using a url-style spec?
>
>   postgres://server:port/dbname
>
> Very fashionable :)

That looks good. But to be really usefule I think we should add both ways
not only to ecpg, but to psql as well.

How about a adding the parser code for both to PQsetdb so we can do:

PQsetdeb(NULL,NULL,NULL,NULL,"postgres://server:port/dbname")

and

PQsetdeb(NULL,NULL,NULL,NULL,"dbname@server:port")

as synonym for

PQsetdb(server,port,NULL,NULL,dbname)?

Michael


--
Dr. Michael Meskes, Project-Manager    | topsystem Systemhaus GmbH
meskes@topsystem.de                    | Europark A2, Adenauerstr. 20
meskes@debian.org                      | 52146 Wuerselen
Go SF49ers! Go Rhein Fire!             | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux!                  | Fax: (+49) 2405/4670-10

pgsql-hackers by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] Decicision needed for connect statement
Next
From: Peter Mount
Date:
Subject: RE: [HACKERS] Decicision needed for connect statement