From: | Michael Meskes <meskes(at)postgreSQL(dot)org> |
---|---|
To: | "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgreSQL(dot)org> |
Cc: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Subject: | Re: [INTERFACES] still cannot connect with pgAdmin |
Date: | 2000-01-04 13:48:25 |
Message-ID: | 20000104144825.A401@fam-meskes.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
On Mon, Jan 03, 2000 at 10:12:14AM -0500, Tom Lane wrote:
> Before you spend too much time digging for a bug in pgAdmin,
> check the possibility that it's connecting to some other database
> server than you think it is. Just a thought...
Unfortunately this is not the problem. I did start the postmaster with
debugging on and see pgAdmin connecting to it. However, I do not see it
asking 'select VERSION()'.
The statements I get through debugging output are:
set DateStyle to 'ISO'
set ksqo to 'ON'
select oid from pg_type where typname='lo'
The type 'lo' however does not exists in this database, i.e. there is no oid
returned. But this hardly looks like a bug in my setup.
Also I only have one connection defined on my M$ machine and with M$ Access
I can see and change all my data.
Is it possible that my ODBC setting are insufficient? I remeber pgAccess
asking for some driver settings I had to enable. But then I did enable them.
Michael
--
Michael Meskes | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz | Go Rhein Fire!
Tel.: (+49) 2431/72651 | Use Debian GNU/Linux!
Email: Michael(at)Fam-Meskes(dot)De | Use PostgreSQL!
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2000-01-04 14:29:59 | RE: [INTERFACES] still cannot connect with pgAdmin |
Previous Message | David Warnock | 2000-01-04 10:12:08 | Re: [GENERAL] Announce: PostgreSQL-6.5.3 binaries available forWindows NT |