On Mon, Jan 08, 2001 at 06:20:42PM +0100, Peter Eisentraut wrote:
> > is not in libpq's current sources anymore. I fully agree with Peter E's
> > reasons for removing it, too. We do not need to overload the definition
> > of libpq's dbname parameter.
Why? Sorry, it seems I missed his mail.
> O
Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> Have you tried it lately? I suspect that you are depending on code that
>> is not in libpq's current sources anymore. I fully agree with Peter E's
>> reasons for removing it, too. We do not need to overload the definition
>> of libpq's dbname para
Tom Lane writes:
> > Not exactly. It is possible to use PGHOST but you also can add the hostname
> > to the dbname.
>
> Have you tried it lately? I suspect that you are depending on code that
> is not in libpq's current sources anymore. I fully agree with Peter E's
> reasons for removing it, to
Michael Meskes <[EMAIL PROTECTED]> writes:
> Anyone willing to spend some time digging the hostname problem? That is why
> ecpg programs need to specify a hostname and not an IP number to connect,
> while psql for instance works with both?
I do not see how that can be ecpg's fault --- it just doe
On Wed, Jan 03, 2001 at 01:20:43AM +0100, Artur Pietruk wrote:
> > try to make a connection to my database, I get the following error at
> > runtime:
> ...
> I'm sorry that I am answering that question after a month, but i
> did not see someone solving your problem.
I did. But I had private
Hello,
I´m trying to use embedded sql with postgresql through ecpg. But if I
try to make a connection to my database, I get the following error at
runtime:
Could not connect to database buecher@localhost in line 18.
(I´m using postgresql 7.0.2)
psql and the jdbc is working, but not the ecpg con
