Обсуждение: connect error

Поиск
Список
Период
Сортировка

connect error

От
綜合システム 支援G 大坪慶子
Дата:
Excuse me.
This is first time that I have ever sent mail to you.

Would you teach me, please!
Why do I get the following error messages?
I have checked on (ODBC Connection Checklist) advice.

ODBC driver version:
PostgreSQL ODBC Driver 07.01.0006

PostgreSQL database version :
PostgreSQL 7.0.2

error messages:
Already connected

psqlodbc.log :
send

sql.log :
send

-----------------------------
Keiko Otsubo
bkootubo@sogonet.co.jp

SOGOSYSTEM Co.,Ltd.JAPAN
-----------------------------


Вложения

Re: connect error

От
Hiroshi Inoue
Дата:
綜合システム 支援G 大坪慶子 wrote:
>
> Excuse me.
> This is first time that I have ever sent mail to you.
>
> Would you teach me, please!
> Why do I get the following error messages?

You seem to have found a bug in our ODBC driver.
I would fix it ASAP.
BTW aren't you using the Japanese version provided
by Hiroki Kataoka ?  What I could provide is the
multibyte version whose use is a little different
from the Japanese version. Is it OK ? Note that
the multibyte version was introduced by Japanese
(Eiji Tokuya). Also note I'm a Japanese and using
the multibyte version.

regards,
Hiroshi Inoue

Re: connect error

От
"Tibor Laszlo"
Дата:
> ODBC driver version:
> PostgreSQL ODBC Driver 07.01.0006
>
> PostgreSQL database version :
> PostgreSQL 7.0.2
>
> error messages:
> Already connected

I apologize for the late respond but only today could I try this.

We get the same "Already connected" error message with C++Builder +
ODBCExpress after every second connection request. We don't know the reason
and the source of the message, so we made a workaround about a year ago. The
error is still coming. Now we use PostgreSQL 7.1.3 and ODBC Driver
07.01.0008/older (under Win98hun/2000hun).

The error appears with the main application connection, which the user can
turn on and off any time. The first time the login seemed correct, then I
logged off and tried to connect again (no matter with what correct user).
Here is the log extract:

conn = 33657616, PGAPI_Connect(DSN='tir', UID='***', PWD='***')
Global Options: Version='07.01.0008', fetch=100, socket=4096,
unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=8190
                disable_optimizer=1, ksqo=1, unique_index=0,
use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0,
bools_as_char=0
                extra_systable_prefixes='dd_;', conn_settings=''
conn_encoding='OTHER'
CONN ERROR: func=PGAPI_Connect, desc='Error on CC_connect', errnum=202,
errmsg='Already connected.'
            ------------------------------------------------------------
            henv=34541424, conn=33657616, status=1, num_stmts=16
            sock=0, stmts=34813072, lobj_type=-999
            ---------------- Socket Info -------------------------------

The next time the connection will be accepted with this OID and PWD or with
any other correct user. Then logoff and connection error again - and so on.
I use the same hdbc all the time.

Note the error comes only with ODBCExpress. We used to use BDE components
without (seeing) this error. Hisoshi, I hope this helps.


Tibor Laszlo
ltibor@mail.tiszanet.hu


Re: connect error

От
Hiroshi Inoue
Дата:
Tibor Laszlo wrote:
>
> > ODBC driver version:
> > PostgreSQL ODBC Driver 07.01.0006
> >
> > PostgreSQL database version :
> > PostgreSQL 7.0.2
> >
> > error messages:
> > Already connected
>
> I apologize for the late respond but only today could I try this.
>
> We get the same "Already connected" error message with C++Builder +
> ODBCExpress after every second connection request. We don't know the reason
> and the source of the message, so we made a workaround about a year ago. The
> error is still coming. Now we use PostgreSQL 7.1.3 and ODBC Driver
> 07.01.0008/older (under Win98hun/2000hun).

My fix isn't committed yet.
Would you try the dll which would hopefully fix the bug ?

regards,
Hiroshi Inoue

Re: connect error

От
"Tibor Laszlo"
Дата:
> My fix isn't committed yet.
> Would you try the dll which would hopefully fix the bug ?

Of course. Where is it?


Tibor Laszlo
ltibor@mail.tiszanet.hu