Re: [HACKERS] libpq PGHOST

2000-10-03 Thread Peter Eisentraut
Tom Lane writes: > I don't see any clear statement in SQL92 that > can't have zero length, so I'm not convinced there's anything wrong here. Hmm, I do: ::= ::= ... ::= | As opposed to, say, an empty character s

Re: [HACKERS] libpq PGHOST

2000-10-02 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > If we were to sort this out, then I think we'd need to change > PQsetdbLogin() to take empty arguments uniformly "as is", and make the > change to make Unix sockets also with an empty host parameter, as > proposed. Then you could use psql -h '' to re

Re: [HACKERS] libpq PGHOST

2000-10-02 Thread Peter Eisentraut
Tom Lane writes: > > The current behaviour of libpq is to use Unix sockets whenever the host > > parameter (PGHOST or setdbLogin argument) is NULL/unset. > > Could we extend that to also use Unix sockets if the parameter is set but > > empty? > Seems reasonable, since the current behavior in that

Re: [HACKERS] libpq PGHOST

2000-10-02 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > The current behaviour of libpq is to use Unix sockets whenever the host > parameter (PGHOST or setdbLogin argument) is NULL/unset. > Could we extend that to also use Unix sockets if the parameter is set but > empty? Seems reasonable, since the curren