Re: ODBC changes
От | Hiroshi Inoue |
---|---|
Тема | Re: ODBC changes |
Дата | |
Msg-id | EKEJJICOHDIEMGPNIFIJGEOCFFAA.Inoue@tpf.co.jp обсуждение исходный текст |
Ответ на | Re: ODBC changes (Dave Page <dpage@vale-housing.co.uk>) |
Список | pgsql-odbc |
> -----Original Message----- > From: Dave Page > > -----Original Message----- > > From: Hiroshi Inoue [mailto:Inoue@tpf.co.jp] > > Sent: 12 September 2001 11:31 > > To: Dave Page > > Cc: pgsql-odbc@postgresql.org > > Subject: Re: [ODBC] ODBC changes > > > > > > Dave Page wrote: > > > > > > Hiroshi, > > > > > > I've been playing with this new version a little and am seeing some > > > differences with the error messages raised. It's difficult to tell > > > exactly what's going on because my own code is somewhat 'in > > limbo' at > > > the moment, but with 07.01.0006, if I try to connect to a server > > > that's not running I > > > get: > > > > > > 2001-09-12 08:51:14 - Error in pgAdmin > > II:frmConnect.cmdConnect_Click: > > > -2147467259 - Could not connect to the server; Could not connect to > > > remote socket. > > > > > > But with 07.01.0007 I get: > > > > > > 2001-09-12 08:54:46 - Error in pgAdmin > > II:frmConnect.cmdConnect_Click: > > > -2147467259 - Unspecified error > > > > > > The errors reported by pgAdmin II are as returned by ADO > > from the ODBC > > > driver. Any ideas? > > > > Hmm it seems to work if I remove ODBC3.0 functions from > > psqlodbc_win32.def. > > Ahh, could it be that ADO is using SQLGetDiagRec instead of > SQLError because > it thinks it's ODBC3.0? If so, that would tie in with some of the other > oddities I've seen with my code (which is calling SQLGetDiagRec directly). OK I would change the driver to not export ODBC3.0 functions together with a bug fix. Anyway ODBC3.0 stuff is only for test. regards, Hiroshi Inoue
В списке pgsql-odbc по дате отправления: